pyusb-users — PyUSB users mailing list discussion

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

[chmedly <ch...@ya...>]

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, 

Re: [pyusb-users] PyUSB backlog

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

Hi Wander,

pyusb is a great project and I certainly hope others can step up
to help you on the project.

On the other hand, please take care of yourself as health is the
most important thing and then followed by family/friends and then
followed by main job/career.


-- 
Xiaofan

Re: [pyusb-users] PyUSB backlog

[Vivek <vv...@gm...>]

Hi wander,

I have used pyUsb in past and I am thankful that it existed. I have been
connected to pyusb through this mail-list only.

I'm taking this opportunity to thank you for your volunteering on this
project.
If it was in my capacity to give you the relief by volunteering I would,
alas I don't know much about pyUsb insides.

So thanks again and I hope we do find a good candidate for taking over
(also that you remain connected with pyUsb).




--
Vivek Yogi

On Sun, Jun 18, 2017 at 8:33 PM, Wander Lairson Costa <
wan...@gm...> wrote:

> Hi there all,
>
> I just would like to let you know why pyusb development has been
> stalled for a while. As you might know, I develop pyusb in my free
> time.
>
> This year things has been quite busy in work, not in terms the work
> hours, but on concentration energy. I work for Mozilla and I was on
> the team responsible to Migrate OSX Firefox automated tests to
> Taskcluster [1]. This was a very hard project that devoted my full
> attention.
>
> Besides that, (and even more important) a couple of years ago I found
> out I suffer from GAD [2] and Depression, and have been treating it
> through medication and therapy since then. For the last past year
> things got really worse, so all energy I had left was canalized to
> keep up with my main job, leaving almost nothing for side projects.
>
> As you might know, mental disorders are not fully understood by
> medicine and treatment takes time to have effects, and it is a role
> coaster in terms of progress. So you might expect a large variance in
> development speed ratio.
>
> I am so sorry for all you who is impacted by unsolved issues and slow
> responses. I hope July or August slowly come back to work on PyUSB.
>
> Finally, I intend to continue pyusb development within my health
> capacity, but this a project belonging to OSS/Free Software (pick
> whatever you prefer), so, if there is someone with more time
> volunteering to lead the project, I am willing to step away as main
> maintainer for the sake of project.
>
>  [1] https://docs.taskcluster.net
>  [2] https://en.wikipedia.org/wiki/Generalized_anxiety_disorder
>
> --
> 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
>

[pyusb-users] PyUSB backlog

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

Hi there all,

I just would like to let you know why pyusb development has been
stalled for a while. As you might know, I develop pyusb in my free
time.

This year things has been quite busy in work, not in terms the work
hours, but on concentration energy. I work for Mozilla and I was on
the team responsible to Migrate OSX Firefox automated tests to
Taskcluster [1]. This was a very hard project that devoted my full
attention.

Besides that, (and even more important) a couple of years ago I found
out I suffer from GAD [2] and Depression, and have been treating it
through medication and therapy since then. For the last past year
things got really worse, so all energy I had left was canalized to
keep up with my main job, leaving almost nothing for side projects.

As you might know, mental disorders are not fully understood by
medicine and treatment takes time to have effects, and it is a role
coaster in terms of progress. So you might expect a large variance in
development speed ratio.

I am so sorry for all you who is impacted by unsolved issues and slow
responses. I hope July or August slowly come back to work on PyUSB.

Finally, I intend to continue pyusb development within my health
capacity, but this a project belonging to OSS/Free Software (pick
whatever you prefer), so, if there is someone with more time
volunteering to lead the project, I am willing to step away as main
maintainer for the sake of project.

 [1] https://docs.taskcluster.net
 [2] https://en.wikipedia.org/wiki/Generalized_anxiety_disorder

-- 
Best Regards,
Wander Lairson Costa

[pyusb-users] Can't find devices on macos

[Brendan S. (eTRIX) <bre...@et...>]

Hi,

I'm using Python3.6 with `pyusb` from PyPI and `libusb1` installed via
HomeBrew, but I can't get my USB devices listed.

It lists standard apple devices, but not my serial ports, etc.  However
`lsusb` does list the devices (it's a bash script that parses the output
of Sytem Profiler or System Information app).

I've read about libusb inf files for Windows (not sure why they're
needed).  Is there something similar required for Mac?

It's seems such a simple thing.  Why can System Information / System
Profiler app find the VID/PID but libusb/pyusb can not?

Thanks, Brendan.

Re: [pyusb-users] usb.core.USBError: [Errno 110] Operation timed out

[Cameron D. <fo...@da...>]

Two points:

1. the core read, write and ctrl_transfer operations have optional
timeout args. (timeout=nnn) value in milliseconds

2. If the timeout is not simply because the you need a longer timeout,
then you might benefit from something like I had to resort to:
trap the USBErorr exception and check the error code.
If it a timeout then you can try to reset/clean up or whatever is
available with your device.
Unfortunately, the timeout code varies with backend, so you need to
knows what that is. If libusb0 then you might have more problems.

Cameron.

On 19-Mar-2017 09:43, Eddie A. Goble wrote:
> Hello all:
> 
> I am using a Raspberry PI 3 in attempts to control my Owi Robotic Arm
> via USB with Python scripting.  I am intermittently getting a "Operation
> timed out" error which halts the code.  75% of the time the program runs
> from start to finish with no problems.  Any ideas on how I can mitigate
> this?  Is there a way to increase the timeout threshold?  Many thanks in
> advance. 
> 
> *Error:*
> 
> Traceback (most recent call last):
> 
>   File "arm2.py", line 59, in <module>
> 
>     MoveArm("ShoulderUp",4.2)
> 
>   File "arm2.py", line 47, in MoveArm
> 
>     RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)
> 
>   File "build/bdist.linux-armv7l/egg/usb/core.py", line 711, in
> ctrl_transfer
> 
>   File "build/bdist.linux-armv7l/egg/usb/backend/libusb1.py", line 836,
> in ctrl_transfer
> 
>   File "build/bdist.linux-armv7l/egg/usb/backend/libusb1.py", line 571,
> in _check
> 
> usb.core.USBError: [Errno 110] Operation timed out
> 
> 
> *From my Python script:*
> 
> import usb.core, usb.util, time, sys
> 
> RoboArm = usb.core.find(idVendor=0x1267, idProduct=0x000)
> 
> if RoboArm is None:
> 
> raise ValueError("Arm not found")
> 
> Duration=1
> 
> def MoveArm(ArmCmd,Duration):
> 
> if ArmCmd == "Base+": 
> 
> print "M5-%s : Rotate base clockwise" % Duration
> 
> ArmCmd=[0,1,0]
> 
> elif ArmCmd == "Base-": 
> 
> print "M5+%s : Rotate base counter clockwise" % Duration
> 
> ArmCmd=[0,2,0]
> 
> elif ArmCmd == "ShoulderDown":
> 
> print "M4-%s : Shoulder down" % Duration
> 
> ArmCmd=[64,0,0]
> 
> elif ArmCmd == "ShoulderUp":
> 
> print "M4+%s : Shoulder up" % Duration
> 
> ArmCmd=[128,0,0]
> 
> elif ArmCmd == "ElbowDown":
> 
> print "M3-%s : Elbow down" % Duration
> 
> ArmCmd=[16,0,0]
> 
> elif ArmCmd == "ElbowUp":
> 
> print "M3+%s : Elbow up" % Duration
> 
> ArmCmd=[32,0,0]
> 
> elif ArmCmd == "WristDown":
> 
> print "M2-%s : Wrist down" % Duration
> 
> ArmCmd=[4,0,0]
> 
> elif ArmCmd == "WristUp":
> 
> print "M2+%s : Wrist up" % Duration
> 
> ArmCmd=[8,0,0]
> 
> elif ArmCmd == "GripClose":
> 
> print "M1-%s : Grip close" % Duration
> 
> ArmCmd=[2,0,0]
> 
> elif ArmCmd == "GripOpen":
> 
> print "M1+%s : Grip open" % Duration
> 
> ArmCmd=[1,0,0]
> 
> elif ArmCmd == "LightOff":
> 
> print "L1-%s : Light off" % Duration
> 
> ArmCmd=[0,0,1]
> 
> elif ArmCmd == "LightOn":
> 
> print "L1+%s : Light on" % Duration
> 
> ArmCmd=[0,0,0]
> 
> else:
> 
> print "Unknown command"
> 
> sys.exit()
> 
> 
> RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)
> 
> time.sleep(Duration)
> 
> ArmCmd=[0,0,0]
> 
> RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)
> 
> 
> #MoveArm("ShoulderUp",.1)
> 
> #sys.exit()
> 
> 
> MoveArm("Base+",7.7)
> 
> MoveArm("ShoulderDown",4)
> 
> MoveArm("ElbowDown",1)
> 
> MoveArm("ElbowUp",1)
> 
> MoveArm("ShoulderUp",4.2)
> 
> MoveArm("Base-",8.4)
> 
> sys.exit()
> 
> Eddie A Goble
> 
> 
> 
> ------------------------------------------------------------------------------
> 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] usb.core.USBError: [Errno 110] Operation timed out

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

Hi Eddie,

This looks like a firmware problem, at least most cases end up being a
firmware bug.

2017-03-18 20:43 GMT-03:00 Eddie A. Goble <edd...@gm...>:
> Hello all:
>
> I am using a Raspberry PI 3 in attempts to control my Owi Robotic Arm via
> USB with Python scripting.  I am intermittently getting a "Operation timed
> out" error which halts the code.  75% of the time the program runs from
> start to finish with no problems.  Any ideas on how I can mitigate this?  Is
> there a way to increase the timeout threshold?  Many thanks in advance.
>
> Error:
>
> Traceback (most recent call last):
>
>   File "arm2.py", line 59, in <module>
>
>     MoveArm("ShoulderUp",4.2)
>
>   File "arm2.py", line 47, in MoveArm
>
>     RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)
>
>   File "build/bdist.linux-armv7l/egg/usb/core.py", line 711, in
> ctrl_transfer
>
>   File "build/bdist.linux-armv7l/egg/usb/backend/libusb1.py", line 836, in
> ctrl_transfer
>
>   File "build/bdist.linux-armv7l/egg/usb/backend/libusb1.py", line 571, in
> _check
>
> usb.core.USBError: [Errno 110] Operation timed out
>
>
> From my Python script:
>
> import usb.core, usb.util, time, sys
>
> RoboArm = usb.core.find(idVendor=0x1267, idProduct=0x000)
>
> if RoboArm is None:
>
> raise ValueError("Arm not found")
>
> Duration=1
>
> def MoveArm(ArmCmd,Duration):
>
> if ArmCmd == "Base+":
>
> print "M5-%s : Rotate base clockwise" % Duration
>
> ArmCmd=[0,1,0]
>
> elif ArmCmd == "Base-":
>
> print "M5+%s : Rotate base counter clockwise" % Duration
>
> ArmCmd=[0,2,0]
>
> elif ArmCmd == "ShoulderDown":
>
> print "M4-%s : Shoulder down" % Duration
>
> ArmCmd=[64,0,0]
>
> elif ArmCmd == "ShoulderUp":
>
> print "M4+%s : Shoulder up" % Duration
>
> ArmCmd=[128,0,0]
>
> elif ArmCmd == "ElbowDown":
>
> print "M3-%s : Elbow down" % Duration
>
> ArmCmd=[16,0,0]
>
> elif ArmCmd == "ElbowUp":
>
> print "M3+%s : Elbow up" % Duration
>
> ArmCmd=[32,0,0]
>
> elif ArmCmd == "WristDown":
>
> print "M2-%s : Wrist down" % Duration
>
> ArmCmd=[4,0,0]
>
> elif ArmCmd == "WristUp":
>
> print "M2+%s : Wrist up" % Duration
>
> ArmCmd=[8,0,0]
>
> elif ArmCmd == "GripClose":
>
> print "M1-%s : Grip close" % Duration
>
> ArmCmd=[2,0,0]
>
> elif ArmCmd == "GripOpen":
>
> print "M1+%s : Grip open" % Duration
>
> ArmCmd=[1,0,0]
>
> elif ArmCmd == "LightOff":
>
> print "L1-%s : Light off" % Duration
>
> ArmCmd=[0,0,1]
>
> elif ArmCmd == "LightOn":
>
> print "L1+%s : Light on" % Duration
>
> ArmCmd=[0,0,0]
>
> else:
>
> print "Unknown command"
>
> sys.exit()
>
>
> RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)
>
> time.sleep(Duration)
>
> ArmCmd=[0,0,0]
>
> RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)
>
>
> #MoveArm("ShoulderUp",.1)
>
> #sys.exit()
>
>
> MoveArm("Base+",7.7)
>
> MoveArm("ShoulderDown",4)
>
> MoveArm("ElbowDown",1)
>
> MoveArm("ElbowUp",1)
>
> MoveArm("ShoulderUp",4.2)
>
> MoveArm("Base-",8.4)
>
> sys.exit()
>
> Eddie A Goble
>
>
> ------------------------------------------------------------------------------
> 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] usb.core.USBError: [Errno 110] Operation timed out

[Eddie A. G. <edd...@gm...>]

Hello all:

I am using a Raspberry PI 3 in attempts to control my Owi Robotic Arm via
USB with Python scripting.  I am intermittently getting a "Operation timed
out" error which halts the code.  75% of the time the program runs from
start to finish with no problems.  Any ideas on how I can mitigate this?
Is there a way to increase the timeout threshold?  Many thanks in advance.

*Error:*

Traceback (most recent call last):

  File "arm2.py", line 59, in <module>

    MoveArm("ShoulderUp",4.2)

  File "arm2.py", line 47, in MoveArm

    RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)

  File "build/bdist.linux-armv7l/egg/usb/core.py", line 711, in
ctrl_transfer

  File "build/bdist.linux-armv7l/egg/usb/backend/libusb1.py", line 836, in
ctrl_transfer

  File "build/bdist.linux-armv7l/egg/usb/backend/libusb1.py", line 571, in
_check

usb.core.USBError: [Errno 110] Operation timed out


*From my Python script:*

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

RoboArm = usb.core.find(idVendor=0x1267, idProduct=0x000)

if RoboArm is None:

raise ValueError("Arm not found")

Duration=1

def MoveArm(ArmCmd,Duration):

if ArmCmd == "Base+":

print "M5-%s : Rotate base clockwise" % Duration

ArmCmd=[0,1,0]

elif ArmCmd == "Base-":

print "M5+%s : Rotate base counter clockwise" % Duration

ArmCmd=[0,2,0]

elif ArmCmd == "ShoulderDown":

print "M4-%s : Shoulder down" % Duration

ArmCmd=[64,0,0]

elif ArmCmd == "ShoulderUp":

print "M4+%s : Shoulder up" % Duration

ArmCmd=[128,0,0]

elif ArmCmd == "ElbowDown":

print "M3-%s : Elbow down" % Duration

ArmCmd=[16,0,0]

elif ArmCmd == "ElbowUp":

print "M3+%s : Elbow up" % Duration

ArmCmd=[32,0,0]

elif ArmCmd == "WristDown":

print "M2-%s : Wrist down" % Duration

ArmCmd=[4,0,0]

elif ArmCmd == "WristUp":

print "M2+%s : Wrist up" % Duration

ArmCmd=[8,0,0]

elif ArmCmd == "GripClose":

print "M1-%s : Grip close" % Duration

ArmCmd=[2,0,0]

elif ArmCmd == "GripOpen":

print "M1+%s : Grip open" % Duration

ArmCmd=[1,0,0]

elif ArmCmd == "LightOff":

print "L1-%s : Light off" % Duration

ArmCmd=[0,0,1]

elif ArmCmd == "LightOn":

print "L1+%s : Light on" % Duration

ArmCmd=[0,0,0]

else:

print "Unknown command"

sys.exit()


RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)

time.sleep(Duration)

ArmCmd=[0,0,0]

RoboArm.ctrl_transfer(0x40,6,0x100,0,ArmCmd,3)


#MoveArm("ShoulderUp",.1)

#sys.exit()


MoveArm("Base+",7.7)

MoveArm("ShoulderDown",4)

MoveArm("ElbowDown",1)

MoveArm("ElbowUp",1)

MoveArm("ShoulderUp",4.2)

MoveArm("Base-",8.4)

sys.exit()

Eddie A Goble

Re: [pyusb-users] Help with ERROR please [usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async]

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

On Wed, Mar 8, 2017 at 9:22 PM, Greg Horler <dr....@gm...> wrote:
> Xiaofan,
>
> I have removed all devices filters using the libusb-win32.exe tool and I
> have not had a crash....yet.
>
> What is/was the purpose of the filter? A lay-man's answer would be good
> please.

For Windows driver it is rather complicated and no layman
answer will probably be available.

In general, you need to have a supported driver in order to use libusb-1.0
Windows and libusb-win32. Most of the cases you will need to switch
the driver from original vendor driver to the support driver.

libusb-win32 library (libusb0.dll): either libusb0.sys (device driver
or filter driver)
or libusbk.sys

libusb-1.0 Windows library (libusb-1.0.dll): either WinUSB.sys or
libusbK.sys (libusb0.sys is not working well, do not use it) or HID
or usbdk.

The filter driver is to enable libusb-win32 library (libusb0.dll)
to be used without replacing the existing vendor driver.

The current version of libusb-win32 device filter is in general safe to use.
It is just it may not work with some device. But it may not work with some
device (eg: those using UMDF driver).

usbdk may be a potential replacement for libusb-win32 filter driver.

In general, libusb-win32 is no longer recommended to be used
for new development. It is recommended to switch to libusb
(libusb-1.0 API).

Ref:
https://github.com/libusb/libusb/wiki/Windows
https://github.com/libusb/libusb/wiki/FAQ
https://sourceforge.net/p/libusb-win32/wiki/Home/


-- 
Xiaofan

Re: [pyusb-users] Help with ERROR please [usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async]

[Greg H. <dr....@gm...>]

Xiaofan,

I have removed all devices filters using the libusb-win32.exe tool and I
have not had a crash....yet.

What is/was the purpose of the filter? A lay-man's answer would be good
please.

Thanks

Greg

-----Original Message-----
From: Xiaofan Chen [mailto:xia...@gm...] 
Sent: 08 March 2017 13:03
To: pyu...@li...
Subject: Re: [pyusb-users] Help with ERROR please [usb.core.USBError: [Errno
None] b'libusb0-dll:err [_usb_reap_async]

On Tue, Mar 7, 2017 at 9:31 PM, Greg Horler <dr....@gm...> wrote:
>> pyusb/libusb may not be the best thing to use for USB HID device.
>
> Why not? The system seems to work other than the erratic time out? Do 
> you have no suggestions as how to fix this problem...
> I would have thought it has been seen before?

This has nothing to do with pyusb but rather the limitation of libusb.

If you use Windows only, you may still want to disable the
libusb-win32 filter and try to use the pyusb libusb-1.0 backend.
It may work better than libusb-win32 filter.

FYI I am the admin of both libusb-win32 project and libusb project.


--
Xiaofan

----------------------------------------------------------------------------
--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
pyusb-users mailing list
pyu...@li...
https://lists.sourceforge.net/lists/listinfo/pyusb-users

Re: [pyusb-users] Help with ERROR please [usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async]

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

On Tue, Mar 7, 2017 at 9:31 PM, Greg Horler <dr....@gm...> wrote:
>> pyusb/libusb may not be the best thing to use for USB HID device.
>
> Why not? The system seems to work other than the erratic
> time out? Do you have no suggestions as how to fix this problem...
> I would have thought it has been seen before?

This has nothing to do with pyusb but rather the limitation of
libusb.

If you use Windows only, you may still want to disable the
libusb-win32 filter and try to use the pyusb libusb-1.0 backend.
It may work better than libusb-win32 filter.

FYI I am the admin of both libusb-win32 project and
libusb project.


-- 
Xiaofan

Re: [pyusb-users] PyUSB Parameters to Diagnose Cold Temperature Problem

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

On Tue, Mar 7, 2017 at 9:16 PM, Greg Horler <dr....@gm...> wrote:
> Sent to Greg Horler by mistake!
>

Not so sure what you mean but take note you are in a public
mailing list and by default you will receive all mailing list posts.

-- 
Xiaofan

Re: [pyusb-users] Help with ERROR please [usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async]

[Greg H. <dr....@gm...>]

Xiaofan, morning, thanks for the reply.

Answers inline.

-----Original Message-----
From: Xiaofan Chen [mailto:xia...@gm...] 
Sent: 07 March 2017 13:08
To: pyu...@li...
Subject: Re: [pyusb-users] Help with ERROR please [usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async]

On Tue, Mar 7, 2017 at 5:33 AM, Greg Horler <dr....@gm...> wrote:
> I have had partial success in interfacing an 8-bit microcontroller 
> with a PC running windows 10,Python and PyUsb.
>
> I am a firmware specialist, i.e. not particularly proficient in 
> Python, I am new to PyUSB.
>
> The problem is that my python program fails periodically with the 
>following  error… ...
> usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async] 
>reaping  request failed, win error: The I/O operation has been aborted 
>because of  either a thread exit or an application request.\r\n\n'
>
> print ("ep.bEndpointAddress = %s" %out_ep_address)
> #print(out_ep_address)
>
> while True:
>
>     dev.write(0x01, [0x81, 0x08, 0x08,0x03,0x04,0x05,0x06,0x07])
>     time.sleep(0.1)  # Sample (0.1)s == 1ms
>     test = dev.read(0x81, 8)
>     print (test)


Did you write the FW by yourself?

>>Partly. The firmware is based on that posted by S Rowloski et al. It has been modified to accommodate new header files provided by microchip etc.
>>The updated firmware works with the C# interface program they created.

Since this is an HID device, are you using the libusb-win32 filter driver?

>> Yes I am. This was used after a lot of Googling

pyusb/libusb may not be the best thing to use for USB HID device.

>>Why not? The system seems to work other than the erratic time out? Do you have no suggestions as how to fix this problem...I would have thought it has been seen before?

If you are saying that PyUSB is unsuitable for HID devices, then this is very annoying, I have dedicated two weeks to getting PyUSB up and running for my project. As writers and maintainers of the code, I would expect such a disclaimer to be placed in a large font at the top of the tutorial / about pages.



Ref: https://github.com/libusb/libusb/wiki/FAQ#does-libusb-support-usb-hid-devices

If you need cross platform HID access, then you may need to look at HIDAPI and its python binding.
   http://www.signal11.us/oss/hidapi/
   https://pypi.python.org/pypi/hidapi

If you only use Python and only care about Windows, you may want to give pywinusb a try.
   https://pypi.python.org/pypi/pywinusb/



--
Xiaofan

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
pyusb-users mailing list
pyu...@li...
https://lists.sourceforge.net/lists/listinfo/pyusb-users

Re: [pyusb-users] PyUSB Parameters to Diagnose Cold Temperature Problem

[Greg H. <dr....@gm...>]

Sent to Greg Horler by mistake!

-----Original Message-----
From: Xiaofan Chen [mailto:xia...@gm...] 
Sent: 07 March 2017 13:16
To: pyu...@li...
Subject: Re: [pyusb-users] PyUSB Parameters to Diagnose Cold Temperature
Problem

On Thu, Feb 23, 2017 at 8:18 PM, Streeter, Samuel S ERDC-RDE-CRREL-NH CIV
<Sam...@er...> wrote:
>
> I'm at a complete loss as to why I'm observing this trend, which is 
> very repeatable. I've isolated the embedded board and tested its 
> functionality in the cold; it's just fine. I've communicated with the 
> manufacturers of the spectrum analyzer, and they do not report any 
> issues with the device at these "near freezing" temperatures, being 
> well above the analyzer's lowest operational temperature of -20 C. 
> Furthermore, when I use the manufacturer's proprietary software to 
> interface with the analyzer, it behaves just fine even at the cooler
temperatures in question.
>

Does the manufacturer's proprietary software run under the embedded board?
If yes, then you have to identify the differences between the proprietary
software and your pyusb application.

If the proprietary software runs under a normal Windows PC and not the
embedded board, then you may have to concentrate on the embedded board
again. When you tests its functionality in code temperature, did you run the
tests with some USB peripherals?


--
Xiaofan

----------------------------------------------------------------------------
--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
pyusb-users mailing list
pyu...@li...
https://lists.sourceforge.net/lists/listinfo/pyusb-users

Re: [pyusb-users] PyUSB Parameters to Diagnose Cold Temperature Problem

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

On Thu, Feb 23, 2017 at 8:18 PM, Streeter, Samuel S ERDC-RDE-CRREL-NH
CIV <Sam...@er...> wrote:
>
> I'm at a complete loss as to why I'm observing this trend, which is very
> repeatable. I've isolated the embedded board and tested its functionality in
> the cold; it's just fine. I've communicated with the manufacturers of the
> spectrum analyzer, and they do not report any issues with the device at
> these "near freezing" temperatures, being well above the analyzer's lowest
> operational temperature of -20 C. Furthermore, when I use the manufacturer's
> proprietary software to interface with the analyzer, it behaves just fine
> even at the cooler temperatures in question.
>

Does the manufacturer's proprietary software run under the embedded
board? If yes, then you have to identify the differences between the
proprietary software and your pyusb application.

If the proprietary software runs under a normal Windows PC and not
the embedded board, then you may have to concentrate on the embedded
board again. When you tests its functionality in code temperature, did you
run the tests with some USB peripherals?


-- 
Xiaofan

Re: [pyusb-users] Help with ERROR please [usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async]

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

On Tue, Mar 7, 2017 at 5:33 AM, Greg Horler <dr....@gm...> wrote:
> I have had partial success in interfacing an 8-bit microcontroller with a PC
> running windows 10,Python and PyUsb.
>
> I am a firmware specialist, i.e. not particularly proficient in Python, I am
> new to PyUSB.
>
> The problem is that my python program fails periodically with the following
> error…
>...
> usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping
> request failed, win error: The I/O operation has been aborted because of
> either a thread exit or an application request.\r\n\n'
>
> print ("ep.bEndpointAddress = %s" %out_ep_address)
> #print(out_ep_address)
>
> while True:
>
>     dev.write(0x01, [0x81, 0x08, 0x08,0x03,0x04,0x05,0x06,0x07])
>     time.sleep(0.1)  # Sample (0.1)s == 1ms
>     test = dev.read(0x81, 8)
>     print (test)


Did you write the FW by yourself?

Since this is an HID device, are you using the libusb-win32 filter driver?
pyusb/libusb may not be the best thing to use for USB HID device.

Ref: https://github.com/libusb/libusb/wiki/FAQ#does-libusb-support-usb-hid-devices

If you need cross platform HID access, then you may need to
look at HIDAPI and its python binding.
   http://www.signal11.us/oss/hidapi/
   https://pypi.python.org/pypi/hidapi

If you only use Python and only care about Windows, you
may want to give pywinusb a try.
   https://pypi.python.org/pypi/pywinusb/



-- 
Xiaofan

[pyusb-users] Help with ERROR please [usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async]

[Greg H. <dr....@gm...>]

Dear ladies and gents, evening.

 

I have had partial success in interfacing an 8-bit microcontroller with a PC
running windows 10,Python and PyUsb.

 

I am a firmware specialist, i.e. not particularly proficient in Python, I am
new to PyUSB.

 

The problem is that my python program fails periodically with the following
error.

 

    raise USBError(errmsg, ret)

usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping
request failed, win error: The I/O operation has been aborted because of
either a thread exit or an application request.\r\n\n'

 

Is this error known? If so is there a "fix" and "What is it?"

 

Any assistance would be gratefully received, as this is an annoying problem
that I desperately need help to fix.

 

Many thanks

 

Greg

 

PS Code and output presented below.

 

 

 

 

 

#!/usr/bin/python
  


import usb.core
import usb.util
import time



# find our device
dev = usb.core.find(idVendor=0x04d8, idProduct=0x01a5)


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

print (dev)
dev.set_configuration()

cfg=dev[0]
intf=cfg[(0,0)]
ep=intf[0]

#print("print ep")
#print(ep)
#print("print cfg")
#print(cfg)
#print("print intf")
#print(intf)

out_ep_address = ep.bEndpointAddress




print ("ep.bEndpointAddress = %s" %out_ep_address)
#print(out_ep_address)

while True:

    dev.write(0x01, [0x81, 0x08, 0x08,0x03,0x04,0x05,0x06,0x07])

    time.sleep(0.1)  # Sample (0.1)s == 1ms

    test = dev.read(0x81, 8)

    print (test)

 

 

 

 

 

 

 

 

C:\Users\User\AppData\Local\Programs\Python\Python36-32\python.exe
"C:/Users/User/Dropbox (Personal)/PyUSB/PyPIC 1.py"

DEVICE ID 04d8:01a5 on Bus 000 Address 001 =================

bLength                :   0x12 (18 bytes)

bDescriptorType        :    0x1 Device

bcdUSB                 :  0x200 USB 2.0

bDeviceClass           :    0x0 Specified at interface

bDeviceSubClass        :    0x0

bDeviceProtocol        :    0x0

bMaxPacketSize0        :    0x8 (8 bytes)

idVendor               : 0x04d8

idProduct              : 0x01a5

bcdDevice              :    0x1 Device 0.01

iManufacturer          :    0x1 DIY Devices

iProduct               :    0x2 16F1455 Generic HID Device

iSerialNumber          :    0x0 

 bNumConfigurations     :    0x1

  CONFIGURATION 1: 100 mA ==================================

   bLength              :    0x9 (9 bytes)

   bDescriptorType      :    0x2 Configuration

   wTotalLength         :   0x29 (41 bytes)

   bNumInterfaces       :    0x1

   bConfigurationValue  :    0x1

   iConfiguration       :    0x0 

   bmAttributes         :   0xa0 Bus Powered, Remote Wakeup

   bMaxPower            :   0x32 (100 mA)

    INTERFACE 0: Human Interface Device ====================

     bLength            :    0x9 (9 bytes)

     bDescriptorType    :    0x4 Interface

     bInterfaceNumber   :    0x0

     bAlternateSetting  :    0x0

     bNumEndpoints      :    0x2

     bInterfaceClass    :    0x3 Human Interface Device

     bInterfaceSubClass :    0x0

     bInterfaceProtocol :    0x0

     iInterface         :    0x0 

      ENDPOINT 0x81: Interrupt IN ==========================

       bLength          :    0x7 (7 bytes)

       bDescriptorType  :    0x5 Endpoint

       bEndpointAddress :   0x81 IN

       bmAttributes     :    0x3 Interrupt

       wMaxPacketSize   :    0x8 (8 bytes)

       bInterval        :    0x1

      ENDPOINT 0x1: Interrupt OUT ==========================

       bLength          :    0x7 (7 bytes)

       bDescriptorType  :    0x5 Endpoint

       bEndpointAddress :    0x1 OUT

       bmAttributes     :    0x3 Interrupt

       wMaxPacketSize   :    0x8 (8 bytes)

       bInterval        :    0x1

ep.bEndpointAddress = 129

array('B', [128, 0, 1, 1, 5, 6, 7, 8])

array('B', [128, 0, 0, 2, 6, 7, 8, 9])

array('B', [128, 0, 1, 3, 7, 8, 9, 10])

array('B', [128, 0, 0, 4, 8, 9, 10, 11])

array('B', [128, 0, 1, 5, 9, 10, 11, 12])

array('B', [128, 0, 0, 6, 10, 11, 12, 13])

array('B', [128, 0, 1, 7, 11, 12, 13, 14])

array('B', [128, 0, 0, 8, 12, 13, 14, 15])

array('B', [128, 0, 1, 9, 13, 14, 15, 16])

Traceback (most recent call last):

  File "C:/Users/User/Dropbox (Personal)/PyUSB/PyPIC 1.py", line 48, in
<module>

    test = dev.read(0x81, 8)

  File
"C:\Users\User\AppData\Local\Programs\Python\Python36-32\lib\site-packages\u
sb\core.py", line 988, in read

    self.__get_timeout(timeout))

  File
"C:\Users\User\AppData\Local\Programs\Python\Python36-32\lib\site-packages\u
sb\backend\libusb0.py", line 560, in intr_read

    timeout)

  File
"C:\Users\User\AppData\Local\Programs\Python\Python36-32\lib\site-packages\u
sb\backend\libusb0.py", line 627, in __read

    timeout

  File
"C:\Users\User\AppData\Local\Programs\Python\Python36-32\lib\site-packages\u
sb\backend\libusb0.py", line 431, in _check

    raise USBError(errmsg, ret)

usb.core.USBError: [Errno None] b'libusb0-dll:err [_usb_reap_async] reaping
request failed, win error: The I/O operation has been aborted because of
either a thread exit or an application request.\r\n\n'

 

Process finished with exit code 1

 

 

 

 

Regards

 

Greg

 

 

Dr Greg Horler

07764 191965

 

[pyusb-users] PyUSB Parameters to Diagnose Cold Temperature Problem

[Streeter, S. S ERDC-RDE-CRREL-NH C. <Sam...@er...>]

Hi all,

I am using the PyUSB 1.0 module with libusb 1.0 for a backend, Python 2.7,
on an embedded Linux system running Debian 7.0 (Wheezy). To describe my
issue, I think that I must provide a little background about my project. I
am using PyUSB to facilitate USB control of  a spectrum analyzer (i.e., a
Spectran HF-60105 V4 X) using the device's API. The embedded computer and
spectrum analyzer are a part of a field deployable system, and as such, the
system must be able to operate at temperatures below freezing (but of
course, above the documented temperature specifications for all hardware).
This is where I run into problems. Specifically, my code works without a
hitch when it is warm outside, but it seems to run into an issue when it's
operating in cooler temperatures (i.e., around freezing). Below is a snippet
of command line output from the Python script when it is warm outside (i.e.,
room temperature), and all is working fine. The hex that follows each API
command is the device's response. The "verify" response is unique, but the
response to all other commands is a generic "/x31/x60/x21/x00", which
confirms reception by the device.

Verify.....................SUCCESSFUL. /x31/x60/x01/x51/x1a/xf5/xaf
Initial boot calib.........SUCCESSFUL. /x31/x60/x21/x00
Preamplifier...............ON. /x31/x60/x21/x00
Attenuation................OFF. /x31/x60/x21/x00
Start frequency........... 99.5 MHz. /x31/x60/x21/x00
Stop frequency............ 101.5 MHz. /x31/x60/x21/x00
RBW....................... 1000 Hz. /x31/x60/x21/x00
Sweep delay accuracy.......ON. /x31/x60/x21/x00
Sweep reset................SUCCESSFUL. /x31/x60/x21/x00

However, when the system is operating in cooler temperatures, near freezing,
the device's responses appear to be delayed. Basically, it appears that the
device.read() commands are timing out without a response at first, but the
device's responses seem to be queued up in a buffer, because eventually
multiple "OK" responses are received by the computer. In the example shown
below, all ends up just fine, because the commands eventually are received
by the analyzer. However, this doesn't always happen, so this glitch is
currently a showstopper for my system. Here's output from the system when
it's around freezing:

Verify.....................FAILED. /x31/x60
Verify.....................SUCCESSFUL.
/x31/x60/x01/x51/x1a/xf5/xaf/x01/x51/x1a/xf5/xaf
Initial boot calib.........FAILED. /x31/x60
Initial boot calib.........FAILED. /x31/x60
Initial boot calib.........FAILED. /x31/x60
Initial boot calib.........SUCCESSFUL.
/x31/x60/x21/x00/x21/x00/x21/x00/x21/x00
Preamplifier set...........FAILED. /x31/x60
Preamplifier set...........FAILED. /x31/x60
Preamplifier set...........FAILED. /x31/x60
Preamplifier...............ON. /x31/x60/x21/x00/x21/x00/x21/x00/x21/x00
Attenuator set.............FAILED. /x31/x60
Attenuator set.............FAILED. /x31/x60
Attenuator set.............FAILED. /x31/x60
Attenuation................OFF. /x31/x60/x21/x00/x21/x00/x21/x00/x21/x00
Start frequency set.......FAILED. /x31/x60
Start frequency set.......FAILED. /x31/x60
Start frequency set.......FAILED. /x31/x60
Start frequency........... 99.5 MHz.
/x31/x60/x21/x00/x21/x00/x21/x00/x21/x00
Stop frequency set........FAILED. /x31/x60
Stop frequency set........FAILED. /x31/x60
Stop frequency............ 101.5 MHz. /x31/x60/x21/x00/x21/x00/x21/x00
RBW set...................FAILED. /x31/x60
RBW set...................FAILED. /x31/x60
RBW set...................FAILED. /x31/x60
RBW....................... 1000 Hz. /x31/x60/x21/x00/x21/x00/x21/x00/x21/x00
Sweep delay accuracy.......FAILED. /x31/x60
Sweep delay accuracy.......FAILED. /x31/x60
Sweep delay accuracy.......FAILED. /x31/x60
Sweep delay accuracy.......ON. /x31/x60/x21/x00/x21/x00/x21/x00/x21/x00
Sweep reset................FAILED. /x31/x60
Sweep reset................FAILED. /x31/x60
Sweep reset................FAILED. /x31/x60
Sweep reset................SUCCESSFUL.
/x31/x60/x21/x00/x21/x00/x21/x00/x21/x00

I'm at a complete loss as to why I'm observing this trend, which is very
repeatable. I've isolated the embedded board and tested its functionality in
the cold; it's just fine. I've communicated with the manufacturers of the
spectrum analyzer, and they do not report any issues with the device at
these "near freezing" temperatures, being well above the analyzer's lowest
operational temperature of -20 C. Furthermore, when I use the manufacturer's
proprietary software to interface with the analyzer, it behaves just fine
even at the cooler temperatures in question.

Tying this back into PyUSB, I'm curious if anyone out there has dealt with
something like this and might have recommendations for USB communication
parameters to adjust or specific PyUSB functions or objects that might help
me diagnose my issue.

Thanks in advance for your time!

Best,

Sam

Re: [pyusb-users] R: Re: libusb error

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

On Thu, Jan 26, 2017 at 10:15 PM, sr...@li... <sr...@li...> wrote:
> Hi Wander,
>
> The files and the symbolic links are under /usr/lib/

Just wondering if you are using 32bit Python and 64bit libusb.
In that case, you may need to install 32bit libusb as well.

What is the OS?


-- 
Xiaofan

[pyusb-users] R: Re: libusb error

[<sr...@li...>]

Hi Wander,

The files and the symbolic links are under /usr/lib/

# ls -l /usr/lib/libusb*
lrwxrwxrwx    1 root     root            19 Jan 24 10:12 /usr/lib/libusb-0.1.
so.4 -> libusb-0.1.so.4.4.4
-rwxr-xr-x    1 root     root         14912 Jan 24 10:34 /usr/lib/libusb-0.1.
so.4.4.4
lrwxrwxrwx    1 root     root            19 Jan 24 09:44 /usr/lib/libusb-1.0.
so -> libusb-1.0.so.0.1.0
lrwxrwxrwx    1 root     root            19 Jan 24 09:44 /usr/lib/libusb-1.0.
so.0 -> libusb-1.0.so.0.1.0
-rwxr-xr-x    1 root     root         84580 Jan 24 10:34 /usr/lib/libusb-1.0.
so.0.1.0
lrwxrwxrwx    1 root     root            19 Jan 24 10:12 /usr/lib/libusb.so -> 
libusb-0.1.so.4.4.4


Regards,

Simone R

>----Messaggio originale----
>Da: "Wander Lairson Costa" <wan...@gm...>
>Data: 26-gen-2017 15.05
>A: "sr...@li..."<sr...@li...>, "pyusb-users"<pyusb-users@lists.
sourceforge.net>
>Ogg: Re: [pyusb-users] libusb error
>
>Where is libusb installed?
>
>2017-01-26 8:57 GMT-02:00 sr...@li... <sr...@li...>:
>> Dear Sirs,
>>
>> I have tried to use pyusb module and I have used a script in order to test
>> it, but the script terminates with an error:
>>
>> 2017-01-26 07:46:41,662 ERROR:usb.libloader:'Libusb 1' could not be found
>> 2017-01-26 07:46:41,685 ERROR:usb.backend.libusb1:Error loading libusb 1.0
>> backend
>> 2017-01-26 07:46:41,795 ERROR:usb.libloader:'OpenUSB library' could not be
>> found
>> 2017-01-26 07:46:41,804 ERROR:usb.backend.openusb:Error loading OpenUSB
>> backend
>> 2017-01-26 07:46:42,098 ERROR:usb.libloader:'Libusb 0' could not be found
>> 2017-01-26 07:46:42,108 ERROR:usb.backend.libusb0:Error loading libusb 0.1
>> backend
>> Traceback (most recent call last):
>>   File "./usbtest.py", line 13, in <module>
>>     dev = usb.core.find(find_all=True)
>>   File
>> "/root/Buildroot/output/target/usr/lib/python3.4/site-packages/usb/core.
py",
>> line 1263, in find
>> usb.core.NoBackendError: No backend available
>>
>>
>> libusb is already installed on the system, but it seems that it is not seen
>> by the module.
>>
>> How can I fix this problem?
>>
>> Thanking you in advance,
>>
>> Simone Rossi
>>
>> 
------------------------------------------------------------------------------
>> 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
>

Re: [pyusb-users] libusb error

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

Where is libusb installed?

2017-01-26 8:57 GMT-02:00 sr...@li... <sr...@li...>:
> Dear Sirs,
>
> I have tried to use pyusb module and I have used a script in order to test
> it, but the script terminates with an error:
>
> 2017-01-26 07:46:41,662 ERROR:usb.libloader:'Libusb 1' could not be found
> 2017-01-26 07:46:41,685 ERROR:usb.backend.libusb1:Error loading libusb 1.0
> backend
> 2017-01-26 07:46:41,795 ERROR:usb.libloader:'OpenUSB library' could not be
> found
> 2017-01-26 07:46:41,804 ERROR:usb.backend.openusb:Error loading OpenUSB
> backend
> 2017-01-26 07:46:42,098 ERROR:usb.libloader:'Libusb 0' could not be found
> 2017-01-26 07:46:42,108 ERROR:usb.backend.libusb0:Error loading libusb 0.1
> backend
> Traceback (most recent call last):
>   File "./usbtest.py", line 13, in <module>
>     dev = usb.core.find(find_all=True)
>   File
> "/root/Buildroot/output/target/usr/lib/python3.4/site-packages/usb/core.py",
> line 1263, in find
> usb.core.NoBackendError: No backend available
>
>
> libusb is already installed on the system, but it seems that it is not seen
> by the module.
>
> How can I fix this problem?
>
> Thanking you in advance,
>
> Simone Rossi
>
> ------------------------------------------------------------------------------
> 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] libusb error

[<sr...@li...>]

Dear Sirs,
I have tried to use pyusb module and I have used a script in order to test it, but the script terminates with an error:
2017-01-26 07:46:41,662 ERROR:usb.libloader:'Libusb 1' could not be found2017-01-26 07:46:41,685 ERROR:usb.backend.libusb1:Error loading libusb 1.0 backend2017-01-26 07:46:41,795 ERROR:usb.libloader:'OpenUSB library' could not be found2017-01-26 07:46:41,804 ERROR:usb.backend.openusb:Error loading OpenUSB backend2017-01-26 07:46:42,098 ERROR:usb.libloader:'Libusb 0' could not be found2017-01-26 07:46:42,108 ERROR:usb.backend.libusb0:Error loading libusb 0.1 backendTraceback (most recent call last):  File "./usbtest.py", line 13, in <module>    dev = usb.core.find(find_all=True)  File "/root/Buildroot/output/target/usr/lib/python3.4/site-packages/usb/core.py", line 1263, in findusb.core.NoBackendError: No backend available

libusb is already installed on the system, but it seems that it is not seen by the module.
How can I fix this problem?
Thanking you in advance,
Simone Rossi

Re: [pyusb-users] Please help to change libusb project website in README.rst

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

On Sat, Jan 14, 2017 at 10:20 PM, Wander Lairson Costa
<wan...@gm...> wrote:
> Sorry for the delay.
> Done: https://github.com/walac/pyusb/commit/fd253184035aff49f2cc4cf2e9f29778b29657bc

Thanks. This is very fast. :-)



-- 
Xiaofan

Re: [pyusb-users] Please help to change libusb project website in README.rst

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

Sorry for the delay.
Done: https://github.com/walac/pyusb/commit/fd253184035aff49f2cc4cf2e9f29778b29657bc

2017-01-12 7:44 GMT-02:00 Xiaofan Chen <xia...@gm...>:
> https://github.com/walac/pyusb/blob/master/README.rst
>
> The above file still points to the old "libusb.org" website. The
> current libusb project website is "libusb.info". Thanks.
>
> Ref: https://github.com/libusb/libusb/wiki/FAQ#libusborg_libusbxorg_and_libusbinfo
>
> --
> Xiaofan
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users



-- 
Best Regards,
Wander Lairson Costa

[pyusb-users] Please help to change libusb project website in README.rst

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

https://github.com/walac/pyusb/blob/master/README.rst

The above file still points to the old "libusb.org" website. The
current libusb project website is "libusb.info". Thanks.

Ref: https://github.com/libusb/libusb/wiki/FAQ#libusborg_libusbxorg_and_libusbinfo

-- 
Xiaofan