Menu
▾
▴
pyusb-users — PyUSB users mailing list discussion
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(4) |
Dec
|
| 2008 |
Jan
(1) |
Feb
(5) |
Mar
(2) |
Apr
|
May
(8) |
Jun
(4) |
Jul
|
Aug
|
Sep
(11) |
Oct
|
Nov
|
Dec
(20) |
| 2009 |
Jan
(16) |
Feb
(7) |
Mar
(9) |
Apr
(4) |
May
(6) |
Jun
(17) |
Jul
(3) |
Aug
(4) |
Sep
(5) |
Oct
(10) |
Nov
(16) |
Dec
|
| 2010 |
Jan
(22) |
Feb
(18) |
Mar
(9) |
Apr
(102) |
May
(29) |
Jun
(40) |
Jul
(80) |
Aug
(21) |
Sep
(47) |
Oct
(13) |
Nov
(19) |
Dec
(45) |
| 2011 |
Jan
(82) |
Feb
(20) |
Mar
(47) |
Apr
(25) |
May
(18) |
Jun
(24) |
Jul
(24) |
Aug
(47) |
Sep
(23) |
Oct
(22) |
Nov
(69) |
Dec
(20) |
| 2012 |
Jan
(56) |
Feb
(42) |
Mar
(43) |
Apr
(27) |
May
(18) |
Jun
(11) |
Jul
(61) |
Aug
(19) |
Sep
(13) |
Oct
(49) |
Nov
(32) |
Dec
(37) |
| 2013 |
Jan
(46) |
Feb
(14) |
Mar
(13) |
Apr
(20) |
May
(20) |
Jun
(3) |
Jul
(19) |
Aug
(7) |
Sep
(4) |
Oct
(33) |
Nov
(7) |
Dec
(15) |
| 2014 |
Jan
(5) |
Feb
(21) |
Mar
(3) |
Apr
(3) |
May
(30) |
Jun
(1) |
Jul
(30) |
Aug
(2) |
Sep
(22) |
Oct
(14) |
Nov
(22) |
Dec
(6) |
| 2015 |
Jan
(7) |
Feb
(4) |
Mar
(16) |
Apr
(9) |
May
(17) |
Jun
(28) |
Jul
(3) |
Aug
(18) |
Sep
(3) |
Oct
|
Nov
(6) |
Dec
(3) |
| 2016 |
Jan
(15) |
Feb
(18) |
Mar
(12) |
Apr
(14) |
May
(15) |
Jun
(3) |
Jul
(3) |
Aug
(42) |
Sep
(24) |
Oct
(6) |
Nov
(5) |
Dec
(6) |
| 2017 |
Jan
(6) |
Feb
(2) |
Mar
(12) |
Apr
|
May
(1) |
Jun
(3) |
Jul
(2) |
Aug
(6) |
Sep
|
Oct
(1) |
Nov
(5) |
Dec
(7) |
| 2018 |
Jan
|
Feb
(9) |
Mar
(7) |
Apr
|
May
(10) |
Jun
(20) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(20) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(9) |
Dec
|
| 2020 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(5) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(8) |
Dec
(2) |
| 2021 |
Jan
(16) |
Feb
(1) |
Mar
|
Apr
(9) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
(1) |
| 2022 |
Jan
|
Feb
(7) |
Mar
|
Apr
(4) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: chris c. <cl...@gm...> - 2016-08-17 14:17:32
|
On Wed, Aug 17, 2016 at 12:31 AM, Hermann Hamann <her...@we...> wrote: > Hi > < would you mind opening a issue? > I will do so, but it may take some time. > I have absolutely no background in Windows and there will be a lot of > googling before > I can present hard facts. > > Therefore I ask the Window gurus among the users to answer me some > questions: > 1. What is the registry for? > 2. Is it valid programming style to disregard registry entries? > 3. Has anyone succesfully used a non registered driver? > Can you clarify #3? I've always had to install the driver, is that what you mean by registered? I've some rough notes on Windows usage at https://bitbucket.org/clach04/coldtears_clock/wiki/Windows On creating issues, it is worth creating it as a place holder and incrementally adding details when you have them. Chris |
|
From: Hermann H. <her...@we...> - 2016-08-17 07:31:32
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div name="quoted-content">Hi</div> <div name="quoted-content">< would you mind opening a issue?</div> <div name="quoted-content">I will do so, but it may take some time.</div> <div name="quoted-content">I have absolutely no background in Windows and there will be a lot of googling before</div> <div name="quoted-content">I can present hard facts.</div> <div name="quoted-content"> </div> <div name="quoted-content">Therefore I ask the Window gurus among the users to answer me some questions:</div> <div name="quoted-content">1. What is the registry for?</div> <div name="quoted-content">2. Is it valid programming style to disregard registry entries?</div> <div name="quoted-content">3. Has anyone succesfully used a non registered driver?</div> <div name="quoted-content"> </div> <div name="quoted-content">Thank you in advance</div> <div name="quoted-content">Hermann Hamann</div> <div name="quoted-content"> </div> </div> </div> </div></div></body></html> |
|
From: Wander L. C. <wan...@gm...> - 2016-08-13 13:03:01
|
Hi,
PyUSB relies on ctypes for finding libraries, which relies on Windows
library search policy, if it finds libusb1 first, then that's what it
assumes as the backend. backend parameter was designed for cases like
yours, when the default backend discovery policy doesn't apply.
Anyway, you code may be helpful to improve the search code, would you
mind opening a issue?
2016-08-13 4:34 GMT-03:00 Hermann Hamann <her...@we...>:
> Dear maintainers,
> my client and I have the same USB-Device. I have written a program for it.
> It runs fine on both Linux systems. It runs fine on my Windows but crashes
> on my client's.
> Both have installed the driver with inf-wizard and the system control shows
> libusb0.dll on
> both machines.
>
> However, pyusb1 does not care about it; there is no single line related to
> the registry in the code.
> Instead pyusb started searching with pyusb1 backend and finds some libusb1
> in some private direcory
> of some other device. And crashed.
>
> This is not acceptable.
> I have written a demo to fetch the correct service from the registry, it
> follows here:
> -------------------------------------------------------------------------------------
> from __future__ import print_function
> # call this only on Windows
> try:
> from _winreg import *
> except:
> from winreg import *
> def getService(vid,pid):
> vidpid = r"\VID_%04x&PID_%04x" % (vid,pid)
> path = r"SYSTEM\ControlSet002\ENUM\USB" + vidpid
> key = OpenKey(HKEY_LOCAL_MACHINE,path,0,KEY_READ)
> try:
> i = 0
> enumkey = EnumKey(key,i)
> i = i + 1
> except Exception as message:
> pass # print("enumkey",message)
>
> newkey = OpenKeyEx(key,enumkey,0,KEY_READ)
> service,Size = QueryValueEx(newkey,"Service")
> return service
> if __name__ == "__main__":
> print ("service for 0x5656 0x0834 is",getService(0x5656,0x0834))
> -----------------------------------------------------------------------------------------
> The output is
> "service for 0x5656 0x0834 is libusb0"
>
> I am aware of the backend=xxx switches and the findlibrary hooks.
> They are useful to override defaults in special cases.
>
> However this does not answer the question which defaults are appropiate in
> the normal case.
> On Windows the registry entry is the most appropriate default.
>
> I hope this can help you to amend pyusb1 (which is a great tool anyway).
>
> Sincerely Hermann Hamann
>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>
--
Best Regards,
Wander Lairson Costa
|
|
From: Hermann H. <her...@we...> - 2016-08-13 07:34:28
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div> <div> <div>Dear maintainers,</div> <div>my client and I have the same USB-Device. I have written a program for it.<br/> It runs fine on both Linux systems. It runs fine on my Windows but crashes on my client's.</div> <div>Both have installed the driver with inf-wizard and the system control shows libusb0.dll on<br/> both machines.</div> <div> </div> <div>However, pyusb1 does not care about it; there is no single line related to the registry in the code.</div> <div>Instead pyusb started searching with pyusb1 backend and finds some libusb1 in some private direcory<br/> of some other device. And crashed.</div> <div> </div> <div>This is not acceptable.</div> <div>I have written a demo to fetch the correct service from the registry, it follows here:</div> <div>-------------------------------------------------------------------------------------</div> <div>from __future__ import print_function</div> <div># call this only on Windows</div> <div>try:<br/> from _winreg import *<br/> except:<br/> from winreg import *</div> <div>def getService(vid,pid):<br/> vidpid = r"\VID_%04x&PID_%04x" % (vid,pid)<br/> path = r"SYSTEM\ControlSet002\ENUM\USB" + vidpid<br/> key = OpenKey(HKEY_LOCAL_MACHINE,path,0,KEY_READ)</div> <div> try:<br/> i = 0<br/> enumkey = EnumKey(key,i)<br/> i = i + 1<br/> except Exception as message:<br/> pass # print("enumkey",message)<br/> <br/> newkey = OpenKeyEx(key,enumkey,0,KEY_READ)<br/> service,Size = QueryValueEx(newkey,"Service")<br/> return service</div> <div>if __name__ == "__main__":<br/> print ("service for 0x5656 0x0834 is",getService(0x5656,0x0834))</div> <div>-----------------------------------------------------------------------------------------</div> <div>The output is<br/> "service for 0x5656 0x0834 is libusb0"</div> <div> </div> <div>I am aware of the backend=xxx switches and the findlibrary hooks.</div> <div>They are useful to override defaults in special cases.</div> <div> </div> <div>However this does not answer the question which defaults are appropiate in the normal case.</div> <div>On Windows the registry entry is the most appropriate default.</div> <div> </div> <div>I hope this can help you to amend pyusb1 (which is a great tool anyway).</div> <div> </div> <div>Sincerely Hermann Hamann</div> <div> </div> <div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"> <div name="quoted-content"> </div> </div> </div> </div></div></body></html> |
|
From: Wander L. C. <wan...@gm...> - 2016-08-02 11:19:55
|
2016-08-02 6:18 GMT-03:00 Hermann Hamann <her...@we...>: > Hello dear maintainers, > Google finds now about 50000 hits on "no backend". So it is time to make an > end to this problem. > > The Problem is two missing lines in the (excellent!) tutorial: > > --------------------------------------------------------------------------------------- > If you encounter "no backend found" messages on Windows (re-)install a > driver for your device > using infwizard from Sourceforge. Otherwise you will fail. > --------------------------------------------------------------------------------------- > > This info would have saved me a month of fruitless poking around. > Hi, in the readme, either libusb or libusb-win32 are dependencies for PyUSB, and in their respectives sites you find the indo for the installation. Maybe this should be explicit in PyUSB readme file. |
|
From: Hermann H. <her...@we...> - 2016-08-02 09:19:04
|
<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hello dear maintainers,</div> <div>Google finds now about 50000 hits on "no backend". So it is time to make an end to this problem.</div> <div> </div> <div>The Problem is two missing lines in the (excellent!) tutorial:</div> <div> </div> <div>---------------------------------------------------------------------------------------</div> <div>If you encounter "no backend found" messages on Windows (re-)install a driver for your device</div> <div>using infwizard from Sourceforge. Otherwise you will fail.</div> <div>---------------------------------------------------------------------------------------</div> <div> </div> <div>This info would have saved me a month of fruitless poking around.</div> <div> </div> <div>Sincerely H. Hamann</div></div></body></html> |
|
From: Richard P. <rpa...@ya...> - 2016-08-01 14:27:02
|
|
0down votefavoriteaaaa | I am trying to interface with a device connected to my Ubuntu 16 system(Python ver 2.7.12)(libusb1.0 and PyUSB installed). When I try to write to the device, I am getting a write timeout (similar with reading from the device).According to what little documentation I have, the HID interface is implemented in interface 3, in addition to the standard endpoint (EP)0 the device supports EP4 IN (device to host) interrupt transfer type, and EP5 OUT( host to device) interrupt transfer type. It also states the USB Bulk is based on request-response message pair with a message format of 64 bytes with the first byte being the 'op code'. For a 'get version' command the op-code is 0x02, and the rest is ignored.I am new to both Python and USB, so probably have this wrong but I am trying to write to the 'OUT' interface and then read from the 'IN' interface. I have noticed that when I plug the device into the Ubuntu system I get a new device /dev/usb/hiddev0 but couldn't seem to write to that with PySerial so tried to connect to interface 3 and grab the In/Out interfaces. Also I added in what I thought was the call for PYUSB_DEBUG but I do not see any more output than without it.With the following code I do see the device, and I get an IN/OUT interface but write/reads always timeout. I do not know what I am missing. Thank you very much for any help.
import usb.core
import usb.util
from usb.core import *
import sys
import os
import binascii
import time
import serial
import itertools
idV = 0x2abf
idP = 0x0505
# doesnt seem to write anything to log?!
os.environ['PYUSB_DEBUG'] = 'debug'
#os.environ['PYUSB_LOG_FILENAME'] = "pyusb.log" #never written
print "finding idVendor = {}, idProduct= {}".format(idV, idP)
device = usb.core.find(idVendor=idV, idProduct=idP)
if device is None:
print ("Device not found")
exit()
# free up the device from the kernal
for cfg in device:
for intf in cfg:
if device.is_kernel_driver_active(intf.bInterfaceNumber):
try:
device.detach_kernel_driver(intf.bInterfaceNumber)
except usb.core.USBError as e:
sys.exit("Could not detach kernel driver from interface({0}): {1}".format(intf.bInterfaceNumber, str(e)))
# try default conf
print "setting configuration"
device.set_configuration()
print "config set"
print "trying to claim device"
try:
usb.util.claim_interface(device, 0)
print "claimed device"
except usb.core.USBError as e:
print "Error occurred claiming " + str(e)
sys.exit("Error occurred on claiming")
print "device claimed"
# get enpoint instance
cfg = device.get_active_configuration()
print "***********"
for intf in cfg:
print "intf= " + str(intf)
print "***********"
# from document:
# The HID interface is implemented on Interface 3, in addition to standard endpoint (er)0, the device supports
# EP4 IN (device to host) interrupt transfer type, and EP5 OUT (host to device) interrupt transfer type
# Note: EP$ seems to come back as 0x84 while EP5 comes back as 0x05
intf = cfg[(3, 0)]
# get the BULK OUT descriptor
epo = usb.util.find_descriptor(
intf,
# match our first out endpoint
custom_match= \
lambda e: \
usb.util.endpoint_direction(e.bEndpointAddress) == \
usb.util.ENDPOINT_OUT)
assert epo is not None
# get the BULK IN descriptor
epi = usb.util.find_descriptor(
intf,
# match our first out endpoint
custom_match= \
lambda e: \
usb.util.endpoint_direction(e.bEndpointAddress) == \
usb.util.ENDPOINT_IN)
assert epi is not None
print "write the data"
# commands are 64 bytes long, first byte is command code, 02 is 'get version', it doesn't need any of the other bytes set
try:
# don't think I can use [0x00]*63 because it will be all pointers to same object?, call them out to be safe
test = [0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00]
mybuff = b'\x02\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
#device.write(epo,mybuff,1) #timeout on write
#epo.write(mybuff) #timeout on write
epo.write(mybuff.encode('utf-8')) #timeout on write
except usb.core.USBError as e:
print "Write USBError: " + str(e)
sys.exit()
print "done writing"
print "try read?"
try:
#info = device.read(0x84, 8)
info = epo.read(epi.bEndpointAddress,epi.wMaxPacketSize)
except usb.core.USBError as e:
print "Read USBError: " + str(e)
sys.exit()
print "read: " + str(info)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=Output:finding idVendor = 10943, idProduct= 1285
setting configuration
config set
trying to claim device
claimed device
device claimed
***********
< skipping audio interfaces>
intf= INTERFACE 3: Human Interface Device ====================
bLength : 0x9 (9 bytes)
bDescriptorType : 0x4 Interface
bInterfaceNumber : 0x3
bAlternateSetting : 0x0
bNumEndpoints : 0x2
bInterfaceClass : 0x3 Human Interface Device
bInterfaceSubClass : 0x0
bInterfaceProtocol : 0x0
iInterface : 0x8 PlaylistControl
ENDPOINT 0x84: Interrupt IN ==========================
bLength : 0x7 (7 bytes)
bDescriptorType : 0x5 Endpoint
bEndpointAddress : 0x84 IN
bmAttributes : 0x3 Interrupt
wMaxPacketSize : 0x40 (64 bytes)
bInterval : 0xa
ENDPOINT 0x5: Interrupt OUT ==========================
bLength : 0x7 (7 bytes)
bDescriptorType : 0x5 Endpoint
bEndpointAddress : 0x5 OUT
bmAttributes : 0x3 Interrupt
wMaxPacketSize : 0x40 (64 bytes)
bInterval : 0xa
***********
write the data
Write USBError: [Errno 110] Operation timed out
|
|
|
From: Mike L. <mik...@gm...> - 2016-07-20 15:09:14
|
Nevermind, solved it! The proper write message is: dev.write(writeEP,"\x01\x03\x06",0) -- Mike Lawrence Graduate Student Department of Psychology & Neuroscience Dalhousie University ~ Certainty is (possibly) folly ~ On Tue, Jul 19, 2016 at 10:28 PM, Mike Lawrence <mik...@gm...> wrote: > Hi all, > > I wonder if anyone might be able to help with this one. I'm looking to use > pyusb to interact with a wired xbox 360 gamepad. So far I can read just > fine but I'd also like to write so I can make the LED stop blinking. > > Looking here ( > http://tattiebogle.net/index.php/ProjectRoot/Xbox360Controller/UsbInfo), > I should be able to do it, but no matter what messages I try sending, I'm > not having any luck controlling the LED. Below is the code I have thus far, > any suggestions? > > import usb > dev = usb.core.find(idVendor=1118, idProduct=654) > dev.set_configuration() > readEP = dev[0][(0,0)][0] #endpoint to read from > writeEP = dev[0][(0,0)][1] #endpoint to write to > > print readEP #should be: <ENDPOINT 0x81: Interrupt IN> > print writeEP #should be: <ENDPOINT 0x1: Interrupt OUT> > > ##read the startup messages > for i in range(4): #usually only 4 messages > data = dev.read(readEP.bEndpointAddress,readEP.wMaxPacketSize,100) > print len(data) #should be 3 > > ##get initial button/axes state > data = dev.read(readEP.bEndpointAddress,readEP.wMaxPacketSize,100) > print len(data) #should be 20 > > ##Try to set the LED to illuminate just one element (message 0x06). > ##Each of the following commented-out attempts fails to leave only the > first > ##element illuminated and subsequent attempts at reading or writing yields > ##"usb.core.USBError: [Errno 5] Input/Output Error" > dev.write(writeEP,'010306',100) > # dev.write(writeEP,'0\x010306',100) > # dev.write(writeEP,'66310',100) #decimal value of 0x010306 > > ##attempt to read again > while True: > data = dev.read(readEP.bEndpointAddress,readEP.wMaxPacketSize,100) > > |
|
From: Mike L. <mik...@gm...> - 2016-07-20 01:29:09
|
Hi all, I wonder if anyone might be able to help with this one. I'm looking to use pyusb to interact with a wired xbox 360 gamepad. So far I can read just fine but I'd also like to write so I can make the LED stop blinking. Looking here ( http://tattiebogle.net/index.php/ProjectRoot/Xbox360Controller/UsbInfo), I should be able to do it, but no matter what messages I try sending, I'm not having any luck controlling the LED. Below is the code I have thus far, any suggestions? import usb dev = usb.core.find(idVendor=1118, idProduct=654) dev.set_configuration() readEP = dev[0][(0,0)][0] #endpoint to read from writeEP = dev[0][(0,0)][1] #endpoint to write to print readEP #should be: <ENDPOINT 0x81: Interrupt IN> print writeEP #should be: <ENDPOINT 0x1: Interrupt OUT> ##read the startup messages for i in range(4): #usually only 4 messages data = dev.read(readEP.bEndpointAddress,readEP.wMaxPacketSize,100) print len(data) #should be 3 ##get initial button/axes state data = dev.read(readEP.bEndpointAddress,readEP.wMaxPacketSize,100) print len(data) #should be 20 ##Try to set the LED to illuminate just one element (message 0x06). ##Each of the following commented-out attempts fails to leave only the first ##element illuminated and subsequent attempts at reading or writing yields ##"usb.core.USBError: [Errno 5] Input/Output Error" dev.write(writeEP,'010306',100) # dev.write(writeEP,'0\x010306',100) # dev.write(writeEP,'66310',100) #decimal value of 0x010306 ##attempt to read again while True: data = dev.read(readEP.bEndpointAddress,readEP.wMaxPacketSize,100) |
|
From: Wander L. C. <wan...@gm...> - 2016-07-02 16:53:48
|
Hi,
I don't know if libusb provides this feature, better to ask in their
mailing list. But you may try through Windows Setup API.
2016-06-20 4:03 GMT-03:00 Igor Bezenchuk <ig...@ho...>:
> Hi,
> I am trying to figure out BDF{Bus;Device;Function} of host with pyusb in
> windows? I get bus value from libusb which is usually a number from
> 1..n(depeanding on number of USB hosts. This is a problem for me because I
> want to identify them based upon their PCIe address. Is there a way to link
> pcie address(BDF) to libusb bus number?
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports. http://sdm.link/zohomanageengine
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>
--
Best Regards,
Wander Lairson Costa
|
|
From: Igor B. <ig...@ho...> - 2016-06-20 07:03:14
|
Hi,I am trying to figure out BDF{Bus;Device;Function} of host with pyusb in windows? I get bus value from libusb which is usually a number from 1..n(depeanding on number of USB hosts. This is a problem for me because I want to identify them based upon their PCIe address. Is there a way to link pcie address(BDF) to libusb bus number? |
|
From: Igor B. <ig...@ho...> - 2016-06-06 09:37:28
|
It's OK, I figure it out. all I need to cast results from code.find() as list devs = list(usb.core.find(find_all=True,idVendor=VID, idProduct=PID)) and then I can iterate over device list and remove host from list. From: ig...@ho... To: pyu...@li... Date: Sun, 5 Jun 2016 16:44:33 +0300 Subject: [pyusb-users] Exclude USB Host from Devices List Hi All,When I try to search for devices under specific host, I always get a list of device that include the host and it's root hub. is there a way to exclude both them, so I get only devices list under a specific Host? ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ pyusb-users mailing list pyu...@li... https://lists.sourceforge.net/lists/listinfo/pyusb-users |
|
From: Igor B. <ig...@ho...> - 2016-06-05 13:44:40
|
Hi All,When I try to search for devices under specific host, I always get a list of device that include the host and it's root hub. is there a way to exclude both them, so I get only devices list under a specific Host? |
|
From: Nicolas P. <nic...@aa...> - 2016-05-17 06:48:51
|
Le 13/05/2016 à 17:36, Jeffrey Nichols a écrit : > On 5/13/2016 10:39 AM, Nicolas Pinault wrote: >> Le 13/05/2016 à 15:10, Jeffrey Nichols a écrit : >> I already tried to use "port_numbers" but this field was always blank. >> After updating libusb-1.0, this field is not blank anymore. >> >> What I don't understand is that bus/port_number numbers are not unique. >> On my system : >> IdVendor8086 IdProduct=1E26 bus=1 Address=1 port=0 >> IdVendor8086 IdProduct=1E2D bus=2 Address=1 port=0 >> * IdVendor0204 IdProduct=6025 bus=1 Address=6 port=1 ports = (1, 6, 1) >> IdVendor0424 IdProduct=2513 bus=1 Address=2 port=6 ports = (1, 6) >> + IdVendor046D IdProduct=C061 bus=2 Address=5 port=1 ports = (1, 1) >> IdVendor0529 IdProduct=0001 bus=1 Address=4 port=5 ports = (1, 5) >> IdVendor2CFF IdProduct=0002 bus=1 Address=5 port=2 ports = (1, 6, 2) >> IdVendor413C IdProduct=2107 bus=2 Address=2 port=2 ports = (1, 2) >> + IdVendor8087 IdProduct=0024 bus=2 Address=4 port=1 ports = (1,) >> * IdVendor8087 IdProduct=0024 bus=1 Address=3 port=1 ports = (1,) >> IdVendor8564 IdProduct=4000 bus=3 Address=20 port=8 ports = (8,) >> IdVendor8086 IdProduct=1E31 bus=3 Address=1 port=0 >> >> The lines marked with a + or a * contains same bus/port_number numbers. >> Only port_numbers field is different. >> What does this mean ? > When the bus is different, they're on totally different USB buses > (presumably this corresponds internally to USB root hubs, I'm not sure > of the technical details). That's always the first level of > differentiation. > Sure. It's so obvious I didn't mentioned it. > The port always corresponds to the final number in the ports tuple. > It's the port number on the last hub in the hierarchy. It's not unique > enough to use to distinguish positions in the hierarchy (even when > combined with bus), and not terribly useful in my opinion. That's what I discovered. Only port_numbers is useful. > > I use the tuple (bus, port_numbers) in my application to determine a > device's physical location, so when I tell a device to reboot into > bootloader mode I can find the new device in the same location (as a > device anywhere else could not be the one I'm looking for). My use case is different but the idea is the same. Nicolas |
|
From: Jeffrey N. <jsn...@su...> - 2016-05-13 15:55:45
|
On 5/13/2016 10:39 AM, Nicolas Pinault wrote: > Le 13/05/2016 à 15:10, Jeffrey Nichols a écrit : >> On 5/13/2016 9:03 AM, Nicolas Pinault wrote: >>> Le 12/05/2016 à 17:15, Wander Lairson Costa a écrit : >>>> 2016-05-12 11:40 GMT-03:00 Nicolas Pinault<nic...@aa...>: >>>>> Hi, >>>>> >>>>> Is it possible to retrieve USB bus topology with PyUSB ? >>>>> >>>> Yes, you will need to use the Device object "port_number" and "bus" properties. >>> While it is enough for my application, I don't see how to >>> reconstruct the USB tree with just "port_number". >> There's also "port_numbers", assuming you're using a somewhat recent >> libusb-1.0 version as your backend. Combine that with the bus >> attribute, and you can get a representation of the physical >> attachment point of the device. > I already tried to use "port_numbers" but this field was always blank. > After updating libusb-1.0, this field is not blank anymore. > > What I don't understand is that bus/port_number numbers are not unique. > On my system : > IdVendor8086 IdProduct=1E26 bus=1 Address=1 port=0 > IdVendor8086 IdProduct=1E2D bus=2 Address=1 port=0 > * IdVendor0204 IdProduct=6025 bus=1 Address=6 port=1 ports = (1, 6, 1) > IdVendor0424 IdProduct=2513 bus=1 Address=2 port=6 ports = (1, 6) > + IdVendor046D IdProduct=C061 bus=2 Address=5 port=1 ports = (1, 1) > IdVendor0529 IdProduct=0001 bus=1 Address=4 port=5 ports = (1, 5) > IdVendor2CFF IdProduct=0002 bus=1 Address=5 port=2 ports = (1, 6, 2) > IdVendor413C IdProduct=2107 bus=2 Address=2 port=2 ports = (1, 2) > + IdVendor8087 IdProduct=0024 bus=2 Address=4 port=1 ports = (1,) > * IdVendor8087 IdProduct=0024 bus=1 Address=3 port=1 ports = (1,) > IdVendor8564 IdProduct=4000 bus=3 Address=20 port=8 ports = (8,) > IdVendor8086 IdProduct=1E31 bus=3 Address=1 port=0 > > The lines marked with a + or a * contains same bus/port_number numbers. > Only port_numbers field is different. > What does this mean ? When the bus is different, they're on totally different USB buses (presumably this corresponds internally to USB root hubs, I'm not sure of the technical details). That's always the first level of differentiation. The port always corresponds to the final number in the ports tuple. It's the port number on the last hub in the hierarchy. It's not unique enough to use to distinguish positions in the hierarchy (even when combined with bus), and not terribly useful in my opinion. I use the tuple (bus, port_numbers) in my application to determine a device's physical location, so when I tell a device to reboot into bootloader mode I can find the new device in the same location (as a device anywhere else could not be the one I'm looking for). Jeff |
|
From: Nicolas P. <nic...@aa...> - 2016-05-13 15:35:41
|
Le 13/05/2016 à 16:39, Nicolas Pinault a écrit : > Le 13/05/2016 à 15:10, Jeffrey Nichols a écrit : >> On 5/13/2016 9:03 AM, Nicolas Pinault wrote: >>> Le 12/05/2016 à 17:15, Wander Lairson Costa a écrit : >>>> 2016-05-12 11:40 GMT-03:00 Nicolas Pinault<nic...@aa...>: >>>>> Hi, >>>>> >>>>> Is it possible to retrieve USB bus topology with PyUSB ? >>>>> >>>> Yes, you will need to use the Device object "port_number" and "bus" properties. >>> While it is enough for my application, I don't see how to >>> reconstruct the USB tree with just "port_number". >> There's also "port_numbers", assuming you're using a somewhat recent >> libusb-1.0 version as your backend. Combine that with the bus >> attribute, and you can get a representation of the physical >> attachment point of the device. > I already tried to use "port_numbers" but this field was always blank. > After updating libusb-1.0, this field is not blank anymore. > > What I don't understand is that bus/port_number numbers are not unique. > On my system : > IdVendor8086 IdProduct=1E26 bus=1 Address=1 port=0 > IdVendor8086 IdProduct=1E2D bus=2 Address=1 port=0 > * IdVendor0204 IdProduct=6025 bus=1 Address=6 port=1 ports = (1, 6, 1) > IdVendor0424 IdProduct=2513 bus=1 Address=2 port=6 ports = (1, 6) > + IdVendor046D IdProduct=C061 bus=2 Address=5 port=1 ports = (1, 1) > IdVendor0529 IdProduct=0001 bus=1 Address=4 port=5 ports = (1, 5) > IdVendor2CFF IdProduct=0002 bus=1 Address=5 port=2 ports = (1, 6, 2) > IdVendor413C IdProduct=2107 bus=2 Address=2 port=2 ports = (1, 2) > + IdVendor8087 IdProduct=0024 bus=2 Address=4 port=1 ports = (1,) > * IdVendor8087 IdProduct=0024 bus=1 Address=3 port=1 ports = (1,) > IdVendor8564 IdProduct=4000 bus=3 Address=20 port=8 ports = (8,) > IdVendor8086 IdProduct=1E31 bus=3 Address=1 port=0 > > The lines marked with a + or a * contains same bus/port_number numbers. > Only port_numbers field is different. > What does this mean ? > After sorting results and analysing further, I understand the whole picture. port_numbers like (1,) references a hub port_numbers like (1, 6, 2) indicate the full path to reach the device (root/hub/device) port_number references the port number of the last hub the device is connected on.. Nicolas |
|
From: Nicolas P. <nic...@aa...> - 2016-05-13 15:15:45
|
Le 13/05/2016 à 15:10, Jeffrey Nichols a écrit : > On 5/13/2016 9:03 AM, Nicolas Pinault wrote: >> Le 12/05/2016 à 17:15, Wander Lairson Costa a écrit : >>> 2016-05-12 11:40 GMT-03:00 Nicolas Pinault<nic...@aa...>: >>>> Hi, >>>> >>>> Is it possible to retrieve USB bus topology with PyUSB ? >>>> >>> Yes, you will need to use the Device object "port_number" and "bus" properties. >> While it is enough for my application, I don't see how to reconstruct >> the USB tree with just "port_number". > There's also "port_numbers", assuming you're using a somewhat recent > libusb-1.0 version as your backend. Combine that with the bus > attribute, and you can get a representation of the physical attachment > point of the device. I already tried to use "port_numbers" but this field was always blank. After updating libusb-1.0, this field is not blank anymore. What I don't understand is that bus/port_number numbers are not unique. On my system : IdVendor8086 IdProduct=1E26 bus=1 Address=1 port=0 IdVendor8086 IdProduct=1E2D bus=2 Address=1 port=0 * IdVendor0204 IdProduct=6025 bus=1 Address=6 port=1 ports = (1, 6, 1) IdVendor0424 IdProduct=2513 bus=1 Address=2 port=6 ports = (1, 6) + IdVendor046D IdProduct=C061 bus=2 Address=5 port=1 ports = (1, 1) IdVendor0529 IdProduct=0001 bus=1 Address=4 port=5 ports = (1, 5) IdVendor2CFF IdProduct=0002 bus=1 Address=5 port=2 ports = (1, 6, 2) IdVendor413C IdProduct=2107 bus=2 Address=2 port=2 ports = (1, 2) + IdVendor8087 IdProduct=0024 bus=2 Address=4 port=1 ports = (1,) * IdVendor8087 IdProduct=0024 bus=1 Address=3 port=1 ports = (1,) IdVendor8564 IdProduct=4000 bus=3 Address=20 port=8 ports = (8,) IdVendor8086 IdProduct=1E31 bus=3 Address=1 port=0 The lines marked with a + or a * contains same bus/port_number numbers. Only port_numbers field is different. What does this mean ? Regards, Nicolas > > Jeff > > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > > > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users -- *Nicolas PINAULT R&D electronics engineer *** ni...@aa... <mailto:ni...@aa...> *AATON-Digital* 38000 Grenoble - France Tel +33 4 7642 9550 http://www.aaton.com http://www.transvideo.eu French Technologies for Film and Digital Cinematography Follow us on Twitter @Aaton_Digital @Transvideo_HD Like us on Facebook https://www.facebook.com/AatonDigital |
|
From: Jeffrey N. <jsn...@su...> - 2016-05-13 13:29:46
|
On 5/13/2016 9:03 AM, Nicolas Pinault wrote: > Le 12/05/2016 à 17:15, Wander Lairson Costa a écrit : >> 2016-05-12 11:40 GMT-03:00 Nicolas Pinault<nic...@aa...>: >>> Hi, >>> >>> Is it possible to retrieve USB bus topology with PyUSB ? >>> >> Yes, you will need to use the Device object "port_number" and "bus" properties. > While it is enough for my application, I don't see how to reconstruct > the USB tree with just "port_number". There's also "port_numbers", assuming you're using a somewhat recent libusb-1.0 version as your backend. Combine that with the bus attribute, and you can get a representation of the physical attachment point of the device. Jeff |
|
From: Nicolas P. <nic...@aa...> - 2016-05-13 13:03:24
|
Le 12/05/2016 à 17:15, Wander Lairson Costa a écrit : > 2016-05-12 11:40 GMT-03:00 Nicolas Pinault <nic...@aa...>: >> Hi, >> >> Is it possible to retrieve USB bus topology with PyUSB ? >> > Yes, you will need to use the Device object "port_number" and "bus" properties. While it is enough for my application, I don't see how to reconstruct the USB tree with just "port_number". > >> Regards, >> Nicolas >> >> -- >> Nicolas PINAULT >> R&D electronics engineer >> ni...@aa... >> >> AATON-Digital >> 38000 Grenoble - France >> Tel +33 4 7642 9550 >> >> http://www.aaton.com >> http://www.transvideo.eu >> French Technologies for Film and Digital Cinematography >> >> Follow us on Twitter >> @Aaton_Digital >> @Transvideo_HD >> >> Like us on Facebook >> https://www.facebook.com/AatonDigital >> >> >> ------------------------------------------------------------------------------ >> Mobile security can be enabling, not merely restricting. Employees who >> bring their own devices (BYOD) to work are irked by the imposition of MDM >> restrictions. Mobile Device Manager Plus allows you to control only the >> apps on BYO-devices by containerizing them, leaving personal data untouched! >> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j >> _______________________________________________ >> pyusb-users mailing list >> pyu...@li... >> https://lists.sourceforge.net/lists/listinfo/pyusb-users >> > > -- *Nicolas PINAULT R&D electronics engineer *** ni...@aa... <mailto:ni...@aa...> *AATON-Digital* 38000 Grenoble - France Tel +33 4 7642 9550 http://www.aaton.com http://www.transvideo.eu French Technologies for Film and Digital Cinematography Follow us on Twitter @Aaton_Digital @Transvideo_HD Like us on Facebook https://www.facebook.com/AatonDigital |
|
From: Wander L. C. <wan...@gm...> - 2016-05-12 15:16:23
|
2016-05-12 11:40 GMT-03:00 Nicolas Pinault <nic...@aa...>: > Hi, > > Is it possible to retrieve USB bus topology with PyUSB ? > Yes, you will need to use the Device object "port_number" and "bus" properties. > > Regards, > Nicolas > > -- > Nicolas PINAULT > R&D electronics engineer > ni...@aa... > > AATON-Digital > 38000 Grenoble - France > Tel +33 4 7642 9550 > > http://www.aaton.com > http://www.transvideo.eu > French Technologies for Film and Digital Cinematography > > Follow us on Twitter > @Aaton_Digital > @Transvideo_HD > > Like us on Facebook > https://www.facebook.com/AatonDigital > > > ------------------------------------------------------------------------------ > Mobile security can be enabling, not merely restricting. Employees who > bring their own devices (BYOD) to work are irked by the imposition of MDM > restrictions. Mobile Device Manager Plus allows you to control only the > apps on BYO-devices by containerizing them, leaving personal data untouched! > https://ad.doubleclick.net/ddm/clk/304595813;131938128;j > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users > -- Best Regards, Wander Lairson Costa |
|
From: Nicolas P. <nic...@aa...> - 2016-05-12 14:40:54
|
Hi, Is it possible to retrieve USB bus topology with PyUSB ? Regards, Nicolas -- *Nicolas PINAULT R&D electronics engineer *** ni...@aa... <mailto:ni...@aa...> *AATON-Digital* 38000 Grenoble - France Tel +33 4 7642 9550 http://www.aaton.com http://www.transvideo.eu French Technologies for Film and Digital Cinematography Follow us on Twitter @Aaton_Digital @Transvideo_HD Like us on Facebook https://www.facebook.com/AatonDigital |
|
From: chris c. <cl...@gm...> - 2016-05-12 01:11:52
|
On Wed, May 11, 2016 at 7:44 AM, Jay Newens <ja...@ne...> wrote: > I was working with my program some more. As I stated in previous posts I > am packaging my program with pyinstaller and have no issues with version > 2.1. Normally I package into one file. I decided to package into one > directory. Doing this I am able to see everything that pyinstaller > packaged. I did the same with pyinstaller version 3.1.1 and compared what > was packaged. The only difference is that pyinstaller version 2.1 has the > libusb dll file in the directory folder and the pyinstaller version 3.1.1 > does not have the dll in the directory folder. I manually moved the dll to > this directory and my program works. For now I can work with the one > directory but it makes my install package with WIX more work but I will be > trying to get the dll into the one file. Not sure what broke but I was able > to figure out what was missing. > Thanks for reporting back. Its probably worth pursuing this with PyInstaller as that sounds like a bug in the new version or perhaps warrants a KB doc if its not considered a bug. I have to confess as I've had such good success with Py2exe in the past (I only need to roll binaries for Windows, not other platforms which is one of PyInstaller key features), Py2exe is pretty good at warning when it thinks it has missed a dll and you can specify how to include them should the need arise, so hopefully that's an option with PyInstaller too? The other thing I like about py2exe is that there are add-ons that create installers for you (you mentioned dealing with Wix), e.g. https://code.google.com/archive/p/py2nsis/, again hopefully there is a similar thing for PyInstaller Chris |
|
From: Jay N. <ja...@ne...> - 2016-05-11 14:44:11
|
Ok, I was working with my program some more. As I stated in previous posts I am packaging my program with pyinstaller and have no issues with version 2.1. Normally I package into one file. I decided to package into one directory. Doing this I am able to see everything that pyinstaller packaged. I did the same with pyinstaller version 3.1.1 and compared what was packaged. The only difference is that pyinstaller version 2.1 has the libusb dll file in the directory folder and the pyinstaller version 3.1.1 does not have the dll in the directory folder. I manually moved the dll to this directory and my program works. For now I can work with the one directory but it makes my install package with WIX more work but I will be trying to get the dll into the one file. Not sure what broke but I was able to figure out what was missing. |
|
From: Jay N. <ja...@ne...> - 2016-05-10 18:06:51
|
Hi Again, I have run this code in my python environment and it returns my backend as expected: import os os.environ['PYUSB_DEBUG'] = 'debug' import usb.core trig = usb.core.find() print trig Response when running code above: <usb.core.Device object at 0x0000000002E0CF98> I even went as far as packaging this with pyinstaller version 3.1.1 and when running the exe I get the same error: C:\Python27\Scripts\dist\testdebug>testdebug.exe Traceback (most recent call last): File "<string>", line 4, in <module> File "usb\core.py", line 846, in find ValueError: No backend available testdebug returned -1 When packaging the code as an exe I do get a warning file with some possibly relevant entries I will list below: missing module named usb.core.USBError - imported by usb.core, usb.backend.libusb10, usb.backend.libusb01, usb.backend.openusb missing module named 'usb.backend.libusb0' - imported by C:\Python27\lib\site-packages\PyInstaller\loader\rthooks\pyi_rth_usb.py missing module named 'usb.backend.libusb1' - imported by C:\Python27\lib\site-packages\PyInstaller\loader\rthooks\pyi_rth_usb.py I have tried using --hidden-backend=usb.backend.libusb10 when packaging and worked with the spec file a bit but none of the help threads online for this issue have helped me. Thanks for your assistance. -----Original Message----- From: Wander Lairson Costa [mailto:wan...@gm...] Sent: Tuesday, May 10, 2016 09:48 To: pyusb-users Subject: Re: [pyusb-users] Issue finding backend when exe created with pyinstaller 3.1.1 One way to investigate what's going on is to set the PYUSB_DEBUG=debug environment variable. 2016-05-09 11:53 GMT-03:00 Jay Newens <ja...@ne...>: > I have been having issues getting my program to run as an exe using > packager pyinstaller version 3.1.1. There is a version 3.2 but it has > other issues so I cannot use it. My program checks the status of the > Zebra KR403 printer and my program works fine in my Python 2.7.9 > environment, PYUsb 1.0.0, on Windows 7, but when I create the exe it > does not work. Pyinstaller 2.1 works ok but my other parts of my > program have been updated and I cannot use it any longer, the list of problems there is too long. > > > > This is how I set up the backend in my code in my python environment: > > > > import usb > > import usb.core > > import usb.util > > import usb.backend.libusb10 as libusb10 > > import sys > > import requests > > dev = usb.core.find(idVendor= int(VID), idProduct= int(PID), > backend=libusb10.get_backend()) > > > > After creating my exe, when I run it from the command prompt I get the > following: > > > > Traceback (most recent call last): > > File "<string>", line 184, in <module> > > File "usb\core.py", line 846, in find > > ValueError: No backend available > > ZebraKR403PaperStatus2.2 returned -1 > > > > I understand that this could be an issue with pyinstaller and I will > report the same issue there. Does anyone else have this issue or have a solution? > > > > Thanks in advance: > > > > Jay > > > > > > > > > > > > > ---------------------------------------------------------------------- > -------- Find and fix application performance issues faster with > Applications Manager Applications Manager provides deep performance > insights into multiple tiers of your business applications. It > resolves application problems quickly and reduces your MTTR. Get your > free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users > -- Best Regards, Wander Lairson Costa ---------------------------------------------------------------------------- -- Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ pyusb-users mailing list pyu...@li... https://lists.sourceforge.net/lists/listinfo/pyusb-users |
|
From: Wander L. C. <wan...@gm...> - 2016-05-10 14:49:16
|
One way to investigate what's going on is to set the PYUSB_DEBUG=debug environment variable. 2016-05-09 11:53 GMT-03:00 Jay Newens <ja...@ne...>: > I have been having issues getting my program to run as an exe using packager > pyinstaller version 3.1.1. There is a version 3.2 but it has other issues so > I cannot use it. My program checks the status of the Zebra KR403 printer and > my program works fine in my Python 2.7.9 environment, PYUsb 1.0.0, on > Windows 7, but when I create the exe it does not work. Pyinstaller 2.1 > works ok but my other parts of my program have been updated and I cannot use > it any longer, the list of problems there is too long. > > > > This is how I set up the backend in my code in my python environment: > > > > import usb > > import usb.core > > import usb.util > > import usb.backend.libusb10 as libusb10 > > import sys > > import requests > > dev = usb.core.find(idVendor= int(VID), idProduct= int(PID), > backend=libusb10.get_backend()) > > > > After creating my exe, when I run it from the command prompt I get the > following: > > > > Traceback (most recent call last): > > File "<string>", line 184, in <module> > > File "usb\core.py", line 846, in find > > ValueError: No backend available > > ZebraKR403PaperStatus2.2 returned -1 > > > > I understand that this could be an issue with pyinstaller and I will report > the same issue there. Does anyone else have this issue or have a solution? > > > > Thanks in advance: > > > > Jay > > > > > > > > > > > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications Manager > Applications Manager provides deep performance insights into multiple tiers > of > your business applications. It resolves application problems quickly and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users > -- Best Regards, Wander Lairson Costa |
13 messages has been excluded from this view by a project administrator.
