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: Xiaofan C. <xia...@gm...> - 2016-03-09 02:46:51
|
On Tue, Mar 8, 2016 at 10:33 PM, Igor Bezenchuk <ig...@ho...> wrote: > I am Interested in generating random bulk traffic with libusb and pyusb > through different bulk devices(i.e Flash drives etc...). > > pyusb does enumerate device and it's endpoints correctly but it fails to > write to them. > as I saw in other posts this issue is well known in windows, my question is > there any way to go around this to write to device's EP in Windows without > installing custom driver with Zadig? > No way under Windows. There is no generic USB driver attaching to all USB device. -- Xiaofan |
|
From: Wander L. C. <wan...@gm...> - 2016-03-08 19:43:13
|
Hi,
I think you may find the answer for your question in libusb mailing list.
2016-03-08 7:32 GMT-08:00 Igor Bezenchuk <ig...@ho...>:
> I am Interested in generating random bulk traffic with libusb and pyusb to
> different bulk devices(i.e Flash drives etc...) ep buffers and check data
> integrity.
> I used this code:
>
> import usb.core
> # I used Gensys usb to sd card reader
> dev = usb.core.find(idVendor=0x05E3 , idProduct=0x0746)
> if dev is None:
> raise ValueError('Device not found')
> for cfg in dev:
> for i in cfg:
> for e in i:
> print e.bmAttributes
> print e.bEndpointAddress
> print ""
> #if you find OUT EP
> if(e.bEndpointAddress == 2):
> e.write(0x00)
> e.write(0x01)
>
>
> and I got this error:
> "raise NotImplementedError(_strerror(ret))
> NotImplementedError: Operation not supported or unimplemented on this
> platform"
>
> pyusb does enumerate device and it's endpoints correctly but it fails to
> write to them.
> as I saw in other posts this issue is well known in windows, my question
> is there any way to go around this to write to device's EP in Windows
> without installing custom driver with Zadig?
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://makebettercode.com/inteldaal-eval
> _______________________________________________
> 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-03-08 15:33:05
|
I am Interested in generating random bulk traffic with libusb and pyusb to different bulk devices(i.e Flash drives etc...) ep buffers and check data integrity.I used this code:import usb.core# I used Gensys usb to sd card readerdev = usb.core.find(idVendor=0x05E3 , idProduct=0x0746)if dev is None: raise ValueError('Device not found')for cfg in dev: for i in cfg: for e in i: print e.bmAttributes print e.bEndpointAddress print "" #if you find OUT EP if(e.bEndpointAddress == 2): e.write(0x00) e.write(0x01) and I got this error:"raise NotImplementedError(_strerror(ret))NotImplementedError: Operation not supported or unimplemented on this platform"pyusb does enumerate device and it's endpoints correctly but it fails to write to them.as I saw in other posts this issue is well known in windows, my question is there any way to go around this to write to device's EP in Windows without installing custom driver with Zadig?
|
|
From: Igor B. <ig...@ho...> - 2016-03-08 14:33:16
|
I am Interested in generating random bulk traffic with libusb and pyusb through different bulk devices(i.e Flash drives etc...). I used this code:
import usb.core# I used Gensys usb to sd card readerdev = usb.core.find(idVendor=0x05E3 , idProduct=0x0746)if dev is None: raise ValueError('Device not found')for cfg in dev: for i in cfg: for e in i: print e.bmAttributes print e.bEndpointAddress print "" #if you find OUT EP if(e.bEndpointAddress == 2): e.write(0x00) e.write(0x01)
and I got this error:"raise NotImplementedError(_strerror(ret))NotImplementedError: Operation not supported or unimplemented on this platform"
pyusb does enumerate device and it's endpoints correctly but it fails to write to them.as I saw in other posts this issue is well known in windows, my question is there any way to go around this to write to device's EP in Windows without installing custom driver with Zadig? |
|
From: Xiaofan C. <xia...@gm...> - 2016-02-27 05:41:41
|
On Fri, Feb 26, 2016 at 5:56 AM, John Coppens <jo...@jc...> wrote: > I rewrote the C program to see if it was faster than pyUSB, but > without hub, the speed is _exactly_ the same. I have been testing up > to 8192 bytes transfer size (I am limited with the device's memory). > > Tomorrow, I will add a test function to check async transfer. > (It being tomorrow already, I did test using libusb in async mode, > but there was no difference at all. If anything, it was 0.5 - 1% > slower). > > I checked, the hub is a single TT version (Genesys Logic Inc). It > does wonders at smaller transfer sizes. At 512, speed goes from > 128kB/s to 508kB/s - wow! As this is in C, you may want to subscribe to libusb mailing list and get some help there. Maybe your device side is not catching up or maybe your host program needs some tuning. libusb mailing list: https://lists.sourceforge.net/lists/listinfo/libusb-devel -- Xiaofan |
|
From: John C. <jo...@jc...> - 2016-02-25 21:56:35
|
On Thu, 25 Feb 2016 13:31:26 +0800 Xiaofan Chen <xia...@gm...> wrote: > I am not so sure if pyusb will allow you to reach the full potential. > > In order to have better speed, increase the transfer size, use async I/O > and then use an external HUB. > Again, very useful. Thanks! I rewrote the C program to see if it was faster than pyUSB, but without hub, the speed is _exactly_ the same. I have been testing up to 8192 bytes transfer size (I am limited with the device's memory). Tomorrow, I will add a test function to check async transfer. (It being tomorrow already, I did test using libusb in async mode, but there was no difference at all. If anything, it was 0.5 - 1% slower). I checked, the hub is a single TT version (Genesys Logic Inc). It does wonders at smaller transfer sizes. At 512, speed goes from 128kB/s to 508kB/s - wow! Cheers, John |
|
From: Xiaofan C. <xia...@gm...> - 2016-02-25 05:40:38
|
On Thu, Feb 25, 2016 at 1:31 PM, Xiaofan Chen <xia...@gm...> wrote: > I am not so sure if pyusb will allow you to reach the full potential. Since this ticker is still open. https://github.com/walac/pyusb/issues/63 > In order to have better speed, increase the transfer size, use async I/O > and then use an external HUB. > > libusb async I/O: http://libusb.sourceforge.net/api-1.0/group__asyncio.html > > I think you will have a good idea by reading the answers from Tsuneo here. > +++++++++++++++++++++++ > http://www.microchip.com/forums/tm.aspx?m=417509 > ... > ++++++++++++++++++++++ > Another advise from another USB expert: Tim Roberts. ++++++++++++++++++ Repeating a speech I give relatively often, remember that USB traffic is all scheduled in advance. The whole frame is laid out ahead of time, and the schedule is sent to the hardware. So, the only requests that will be present in a frame are those that were already pending when the host controller driver started to create the schedule. After it is submitted, any new requests will be scheduled into the NEXT frame. A full-speed frame can transfer about 1200 bytes. If you expect to be able to transfer that much data, then you must submit 1200 bytes worth of requests before the frame begins. ++++++++++++++++++ -- Xiaofan |
|
From: Xiaofan C. <xia...@gm...> - 2016-02-25 05:31:34
|
On Thu, Feb 25, 2016 at 12:32 AM, John Coppens <jo...@jc...> wrote: > Xiafan, after much tinkering with the C program, I was too impatient to get > things working, so I restarted from zero (again from the original usb_dev_bulk > demo, and a host program with pyUSB in the PC. I appreciate your input though, > and it was very helpful in avoiding the same problem this time. > > I was able to get these results (all at 'Full' speed): > > 1 external hub No external hub > Transfer size Throughput (B/s) Throughput (B/s) > 512 433120 128000 > 768 519300 145699 > 1024 433120 204811 > 2048 619329 341322 > 4096 658343 455133 > 8192 668429 585411 > > Both seem to flatten out too early. Though the speed at 8192 is enough for > me, any idea why the speed does not go nearer 1.2MB/s? And why the speed > at small transfer sizes is so different without hub? > I am not so sure if pyusb will allow you to reach the full potential. In order to have better speed, increase the transfer size, use async I/O and then use an external HUB. libusb async I/O: http://libusb.sourceforge.net/api-1.0/group__asyncio.html I think you will have a good idea by reading the answers from Tsuneo here. +++++++++++++++++++++++ http://www.microchip.com/forums/tm.aspx?m=417509 Example: Tsuneo's explanations on the usage of hub The performance will be achieved under these conditions. a) Single device on the bus Connect the device to the PC USB port directly, as you did. b) Over single TT (Transaction Translator) hub, without any other Full-/Low-speed device You can use a hub between the device and the PC. Rather, it speeds up the bulk transfer of the device. Hi-speed devices on the same hub doesn't disturb the Full-/Low-speed device. c) Over multiple TT hub In this case, you can use other Full-/Low-speed devices on the hub. The hub assigns full Full-/Low-speed bandwidth to each device on its ports. Most of Hi-Speed hubs on the market (usually, called as USB2.0 hub) are single-TT. Multi-TT hubs Belkin F5U234v1 http://catalog.belkin.com/IWCatProductPage.process?Product_Id=159070 IOGEAR GUH274 http://www.iogear.com/product/GUH274/ Tsuneo ++++++++++++++++++++++ -- Xiaofan |
|
From: John C. <jo...@jc...> - 2016-02-24 18:14:20
|
On Tue, 23 Feb 2016 09:35:48 +0800 Xiaofan Chen <xia...@gm...> wrote: > Xiaofan Sorry - the plot has the wrong labels in the Legend. Of course the higher throughput was via the external hub. John |
|
From: John C. <jo...@jc...> - 2016-02-24 16:33:02
|
On Tue, 23 Feb 2016 09:35:48 +0800 Xiaofan Chen <xia...@gm...> wrote: > On Tue, Feb 23, 2016 at 1:29 AM, John Coppens <jo...@jc...> wrote: > >> You can set LIBUSB_DEBUG=4 before running your pyusb program > >> and then post the verbose libusb debug info. > > > > Here's the full debug output. Note that there is a 5 second wait before the set_configuration > > times out (is this the default value?). > > [ 0.004829] [000003da] libusb: debug [libusb_kernel_driver_active] interface 1 > > [ 0.004853] [000003da] libusb: debug [libusb_get_config_descriptor] index 0 > > [ 0.004911] [000003da] libusb: debug [libusb_set_configuration] configuration 1 > > [ 5.004752] [000003da] libusb: error [op_set_configuration] failed, error -1 errno 110 > > Errono is ETIMEDOUT. This is a bit strange. It might be that your > FW is faulty. > > > When tested with a minimalistic C program, also with libusb 1.0.20, > > the transfer actually starts, but stops after a couple of 512 > > data blocks. > > What is your minimalist C program? Does it call libusb_set_configuration()? > If not, please add it to see if that cause problem or not. > > In reality libusb_set_configuration() is in generally not needed in libusb > (other than those special device with two or more configurations), the > only exception is for libusb-win32 (may need to call usb_set_configuration) > which pyusb supports. Xiafan, after much tinkering with the C program, I was too impatient to get things working, so I restarted from zero (again from the original usb_dev_bulk demo, and a host program with pyUSB in the PC. I appreciate your input though, and it was very helpful in avoiding the same problem this time. I was able to get these results (all at 'Full' speed): 1 external hub No external hub Transfer size Throughput (B/s) Throughput (B/s) 512 433120 128000 768 519300 145699 1024 433120 204811 2048 619329 341322 4096 658343 455133 8192 668429 585411 Both seem to flatten out too early. Though the speed at 8192 is enough for me, any idea why the speed does not go nearer 1.2MB/s? And why the speed at small transfer sizes is so different without hub? I attached a graph of the above - I don't know if the list allows attachments. Cheers, John |
|
From: Xiaofan C. <xia...@gm...> - 2016-02-23 01:35:54
|
On Tue, Feb 23, 2016 at 1:29 AM, John Coppens <jo...@jc...> wrote: >> You can set LIBUSB_DEBUG=4 before running your pyusb program >> and then post the verbose libusb debug info. > > Here's the full debug output. Note that there is a 5 second wait before the set_configuration > times out (is this the default value?). > [ 0.004829] [000003da] libusb: debug [libusb_kernel_driver_active] interface 1 > [ 0.004853] [000003da] libusb: debug [libusb_get_config_descriptor] index 0 > [ 0.004911] [000003da] libusb: debug [libusb_set_configuration] configuration 1 > [ 5.004752] [000003da] libusb: error [op_set_configuration] failed, error -1 errno 110 Errono is ETIMEDOUT. This is a bit strange. It might be that your FW is faulty. > When tested with a minimalistic C program, also with libusb 1.0.20, > the transfer actually starts, but stops after a couple of 512 > data blocks. What is your minimalist C program? Does it call libusb_set_configuration()? If not, please add it to see if that cause problem or not. In reality libusb_set_configuration() is in generally not needed in libusb (other than those special device with two or more configurations), the only exception is for libusb-win32 (may need to call usb_set_configuration) which pyusb supports. -- Xiaofan |
|
From: John C. <jo...@jc...> - 2016-02-22 17:29:46
|
On Mon, 22 Feb 2016 09:20:12 +0800
Xiaofan Chen <xia...@gm...> wrote:
> > - In C, I have code that detaches the kernel driver if necessary. Is this necessary
> > here? I didn't find any reference in the tutorial.
>
> Yes, if there is a kernel driver (except usbfs) bind to the device.
Thanks for the reply, Xiaofan.
I added:
if dev.is_kernel_driver_active(1):
dev.detach_kernel_driver(1)
print("Kernel detached")
but it didn't make much difference (see below)
> You can set LIBUSB_DEBUG=4 before running your pyusb program
> and then post the verbose libusb debug info.
Here's the full debug output. Note that there is a 5 second wait before the set_configuration
times out (is this the default value?).
[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.000001] [000003da] libusb: debug [libusb_init] created default context
[ 0.000041] [000003da] libusb: debug [libusb_init] libusb v1.0.20.11004
[ 0.000062] [000003da] libusb: debug [find_usbfs_path] found usbfs at /dev/bus/usb
[ 0.000079] [000003da] libusb: debug [op_init] bulk continuation flag supported
[ 0.000088] [000003da] libusb: debug [op_init] zero length packet flag supported
[ 0.000103] [000003da] libusb: debug [op_init] sysfs can relate devices
[ 0.000112] [000003da] libusb: debug [op_init] sysfs has complete descriptors
[ 0.000354] [0000041b] libusb: debug [linux_udev_event_thread_main] udev event thread entering.
[ 0.000782] [000003da] libusb: debug [linux_get_device_address] getting address for device: usb3 detached: 0
[ 0.000803] [000003da] libusb: debug [linux_get_device_address] scan usb3
[ 0.000856] [000003da] libusb: debug [linux_get_device_address] bus=3 dev=1
[ 0.000869] [000003da] libusb: debug [linux_enumerate_device] busnum 3 devaddr 1 session_id 769
[ 0.000880] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 3/1 (session 769)
[ 0.000988] [000003da] libusb: debug [linux_get_device_address] getting address for device: 3-1 detached: 0
[ 0.001002] [000003da] libusb: debug [linux_get_device_address] scan 3-1
[ 0.001052] [000003da] libusb: debug [linux_get_device_address] bus=3 dev=2
[ 0.001064] [000003da] libusb: debug [linux_enumerate_device] busnum 3 devaddr 2 session_id 770
[ 0.001074] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 3/2 (session 770)
[ 0.001119] [000003da] libusb: debug [linux_get_parent_info] Dev 0x1d29300 (3-1) has parent 0x1d29240 (usb3) port 1
[ 0.001200] [000003da] libusb: debug [linux_get_device_address] getting address for device: usb4 detached: 0
[ 0.001212] [000003da] libusb: debug [linux_get_device_address] scan usb4
[ 0.001261] [000003da] libusb: debug [linux_get_device_address] bus=4 dev=1
[ 0.001274] [000003da] libusb: debug [linux_enumerate_device] busnum 4 devaddr 1 session_id 1025
[ 0.001284] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 4/1 (session 1025)
[ 0.001400] [000003da] libusb: debug [linux_get_device_address] getting address for device: usb1 detached: 0
[ 0.001413] [000003da] libusb: debug [linux_get_device_address] scan usb1
[ 0.001465] [000003da] libusb: debug [linux_get_device_address] bus=1 dev=1
[ 0.001487] [000003da] libusb: debug [linux_enumerate_device] busnum 1 devaddr 1 session_id 257
[ 0.001496] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 1/1 (session 257)
[ 0.001582] [000003da] libusb: debug [linux_get_device_address] getting address for device: 1-2 detached: 0
[ 0.001593] [000003da] libusb: debug [linux_get_device_address] scan 1-2
[ 0.001636] [000003da] libusb: debug [linux_get_device_address] bus=1 dev=3
[ 0.001644] [000003da] libusb: debug [linux_enumerate_device] busnum 1 devaddr 3 session_id 259
[ 0.001652] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 1/3 (session 259)
[ 0.001691] [000003da] libusb: debug [linux_get_parent_info] Dev 0x1d29f10 (1-2) has parent 0x1d29e50 (usb1) port 2
[ 0.001760] [000003da] libusb: debug [linux_get_device_address] getting address for device: 1-3 detached: 0
[ 0.001769] [000003da] libusb: debug [linux_get_device_address] scan 1-3
[ 0.001812] [000003da] libusb: debug [linux_get_device_address] bus=1 dev=4
[ 0.001820] [000003da] libusb: debug [linux_enumerate_device] busnum 1 devaddr 4 session_id 260
[ 0.001828] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 1/4 (session 260)
[ 0.001866] [000003da] libusb: debug [linux_get_parent_info] Dev 0x1d2b060 (1-3) has parent 0x1d29e50 (usb1) port 3
[ 0.001910] [000003da] libusb: debug [linux_get_device_address] getting address for device: 1-3.1 detached: 0
[ 0.001920] [000003da] libusb: debug [linux_get_device_address] scan 1-3.1
[ 0.001962] [000003da] libusb: debug [linux_get_device_address] bus=1 dev=6
[ 0.001970] [000003da] libusb: debug [linux_enumerate_device] busnum 1 devaddr 6 session_id 262
[ 0.001978] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 1/6 (session 262)
[ 0.002016] [000003da] libusb: debug [linux_get_parent_info] Dev 0x1d2b510 (1-3.1) has parent 0x1d2b060 (1-3) port 1
[ 0.002070] [000003da] libusb: debug [linux_get_device_address] getting address for device: 1-3.1.4 detached: 0
[ 0.002079] [000003da] libusb: debug [linux_get_device_address] scan 1-3.1.4
[ 0.002126] [000003da] libusb: debug [linux_get_device_address] bus=1 dev=10
[ 0.002134] [000003da] libusb: debug [linux_enumerate_device] busnum 1 devaddr 10 session_id 266
[ 0.002142] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 1/10 (session 266)
[ 0.002180] [000003da] libusb: debug [linux_get_parent_info] Dev 0x1d2b9c0 (1-3.1.4) has parent 0x1d2b510 (1-3.1) port 4
[ 0.002290] [000003da] libusb: debug [linux_get_device_address] getting address for device: 1-3.4 detached: 0
[ 0.002301] [000003da] libusb: debug [linux_get_device_address] scan 1-3.4
[ 0.002344] [000003da] libusb: debug [linux_get_device_address] bus=1 dev=7
[ 0.002353] [000003da] libusb: debug [linux_enumerate_device] busnum 1 devaddr 7 session_id 263
[ 0.002361] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 1/7 (session 263)
[ 0.002414] [000003da] libusb: debug [linux_get_parent_info] Dev 0x1d2be90 (1-3.4) has parent 0x1d2b060 (1-3) port 4
[ 0.002645] [000003da] libusb: debug [linux_get_device_address] getting address for device: usb5 detached: 0
[ 0.002657] [000003da] libusb: debug [linux_get_device_address] scan usb5
[ 0.002705] [000003da] libusb: debug [linux_get_device_address] bus=5 dev=1
[ 0.002716] [000003da] libusb: debug [linux_enumerate_device] busnum 5 devaddr 1 session_id 1281
[ 0.002726] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 5/1 (session 1281)
[ 0.002841] [000003da] libusb: debug [linux_get_device_address] getting address for device: usb6 detached: 0
[ 0.002853] [000003da] libusb: debug [linux_get_device_address] scan usb6
[ 0.002911] [000003da] libusb: debug [linux_get_device_address] bus=6 dev=1
[ 0.002923] [000003da] libusb: debug [linux_enumerate_device] busnum 6 devaddr 1 session_id 1537
[ 0.002933] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 6/1 (session 1537)
[ 0.003055] [000003da] libusb: debug [linux_get_device_address] getting address for device: usb2 detached: 0
[ 0.003068] [000003da] libusb: debug [linux_get_device_address] scan usb2
[ 0.003116] [000003da] libusb: debug [linux_get_device_address] bus=2 dev=1
[ 0.003129] [000003da] libusb: debug [linux_enumerate_device] busnum 2 devaddr 1 session_id 513
[ 0.003139] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 2/1 (session 513)
[ 0.003241] [000003da] libusb: debug [linux_get_device_address] getting address for device: 2-2 detached: 0
[ 0.003251] [000003da] libusb: debug [linux_get_device_address] scan 2-2
[ 0.003292] [000003da] libusb: debug [linux_get_device_address] bus=2 dev=2
[ 0.003300] [000003da] libusb: debug [linux_enumerate_device] busnum 2 devaddr 2 session_id 514
[ 0.003308] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 2/2 (session 514)
[ 0.003344] [000003da] libusb: debug [linux_get_parent_info] Dev 0x1d2d1b0 (2-2) has parent 0x1d2cce0 (usb2) port 2
[ 0.003428] [000003da] libusb: debug [linux_get_device_address] getting address for device: usb7 detached: 0
[ 0.003441] [000003da] libusb: debug [linux_get_device_address] scan usb7
[ 0.003482] [000003da] libusb: debug [linux_get_device_address] bus=7 dev=1
[ 0.003490] [000003da] libusb: debug [linux_enumerate_device] busnum 7 devaddr 1 session_id 1793
[ 0.003498] [000003da] libusb: debug [linux_enumerate_device] allocating new device for 7/1 (session 1793)
[ 0.003573] [000003da] libusb: debug [usbi_add_pollfd] add fd 6 events 1
[ 0.003585] [000003da] libusb: debug [usbi_io_init] using timerfd for timeouts
[ 0.003593] [000003da] libusb: debug [usbi_add_pollfd] add fd 9 events 1
[ 0.003670] [000003da] libusb: debug [libusb_get_device_list]
[ 0.003684] [000003da] libusb: debug [discovered_devs_append] need to increase capacity
[ 0.003745] [000003da] libusb: debug [libusb_get_device_descriptor]
[ 0.003888] [000003da] libusb: debug [libusb_get_device_descriptor]
[ 0.003993] [000003da] libusb: debug [libusb_get_device_descriptor]
[ 0.004058] [000003da] libusb: debug [libusb_get_device_descriptor]
[ 0.004123] [000003da] libusb: debug [libusb_get_device_descriptor]
[ 0.004187] [000003da] libusb: debug [libusb_get_device_descriptor]
[ 0.004252] [000003da] libusb: debug [libusb_get_device_descriptor]
[ 0.004330] [000003da] libusb: debug [libusb_get_config_descriptor] index 0
1
[ 0.004435] [000003da] libusb: debug [libusb_get_config_descriptor] index 0
0,0
[ 0.004545] [000003da] libusb: debug [libusb_get_config_descriptor] index 0
129
[ 0.004637] [000003da] libusb: debug [libusb_get_config_descriptor] index 0
1
[ 0.004726] [000003da] libusb: debug [libusb_get_config_descriptor] index 0
[ 0.004783] [000003da] libusb: debug [libusb_open] open 1.10
[ 0.004810] [000003da] libusb: debug [usbi_add_pollfd] add fd 10 events 4
[ 0.004829] [000003da] libusb: debug [libusb_kernel_driver_active] interface 1
[ 0.004853] [000003da] libusb: debug [libusb_get_config_descriptor] index 0
[ 0.004911] [000003da] libusb: debug [libusb_set_configuration] configuration 1
[ 5.004752] [000003da] libusb: error [op_set_configuration] failed, error -1 errno 110
Traceback (most recent call last):
File "./test_pyusb.py", line 82, in <module>
sys.exit(main(sys.argv))
File "./test_pyusb.py", line 73, in main
dev.set_configuration()
File "/usr/lib64/python2.7/site-packages/usb/core.py", line 819, in set_configuration
self._ctx.managed_set_configuration(self, configuration)
File "/usr/lib64/python2.7/site-packages/usb/core.py", line 129, in managed_set_configuration
self.backend.set_configuration(self.handle, cfg.bConfigurationValue)
File "/usr/lib64/python2.7/site-packages/usb/backend/libusb1.py", line 786, in set_configuration
_check(self.lib.libusb_set_configuration(dev_handle.handle, config_value))
File "/usr/lib64/python2.7/site-packages/usb/backend/libusb1.py", line 592, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno None] Other error
[ 5.007842] [000003da] libusb: debug [libusb_close]
[ 5.007861] [000003da] libusb: debug [usbi_remove_pollfd] remove fd 10
[ 5.007894] [000003da] libusb: debug [libusb_exit]
[ 5.007904] [000003da] libusb: debug [libusb_exit] destroying default context
[ 5.007915] [000003da] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 5.007925] [000003da] libusb: debug [handle_events] poll fds modified, reallocating
[ 5.007937] [000003da] libusb: debug [handle_events] poll() 2 fds with timeout in 0ms
[ 5.007947] [000003da] libusb: debug [handle_events] poll() returned 0
[ 5.007957] [000003da] libusb: debug [libusb_unref_device] destroy device 7.1
[ 5.007967] [000003da] libusb: debug [libusb_unref_device] destroy device 2.2
[ 5.007975] [000003da] libusb: debug [libusb_unref_device] destroy device 2.1
[ 5.007984] [000003da] libusb: debug [libusb_unref_device] destroy device 6.1
[ 5.007992] [000003da] libusb: debug [libusb_unref_device] destroy device 5.1
[ 5.008002] [000003da] libusb: debug [libusb_unref_device] destroy device 1.7
[ 5.008011] [000003da] libusb: debug [libusb_unref_device] destroy device 1.10
[ 5.008019] [000003da] libusb: debug [libusb_unref_device] destroy device 1.6
[ 5.008028] [000003da] libusb: debug [libusb_unref_device] destroy device 1.4
[ 5.008037] [000003da] libusb: debug [libusb_unref_device] destroy device 1.3
[ 5.008047] [000003da] libusb: debug [libusb_unref_device] destroy device 1.1
[ 5.008056] [000003da] libusb: debug [libusb_unref_device] destroy device 4.1
[ 5.008065] [000003da] libusb: debug [libusb_unref_device] destroy device 3.2
[ 5.008074] [000003da] libusb: debug [libusb_unref_device] destroy device 3.1
[ 5.008083] [000003da] libusb: debug [usbi_remove_pollfd] remove fd 6
[ 5.008098] [000003da] libusb: debug [usbi_remove_pollfd] remove fd 9
[ 5.008129] [0000041b] libusb: debug [linux_udev_event_thread_main] udev event thread exiting
|
|
From: Xiaofan C. <xia...@gm...> - 2016-02-22 01:20:18
|
On Mon, Feb 22, 2016 at 8:57 AM, John Coppens <jo...@jc...> wrote: > When tested with a minimalistic C program, also with libusb 1.0.20, the transfer > actually starts, but stops after a couple of 512 data blocks. > > Questions: > - In C, I have code that detaches the kernel driver if necessary. Is this necessary > here? I didn't find any reference in the tutorial. Yes, if there is a kernel driver (except usbfs) bind to the device. > - Any other tests I can do? > > The system is Linux, kernel 4.1.6, Slackware 14.1, and > libusb 1.0.20. You can set LIBUSB_DEBUG=4 before running your pyusb program and then post the verbose libusb debug info. -- Xiaofan |
|
From: John C. <jo...@jc...> - 2016-02-22 00:57:13
|
Hi all.
I wrote a simple program to communicate with a USB peripheral which is supposed
to send A/D samples to the host by bulk transfer.
I have the impression that the enumeration is normal (see lsusb -v output below).
When the program:
def main(args):
dev = usb.core.find(idVendor = VID, idProduct = PID)
if dev is None:
raise ValueError('Device not found')
dump_interfaces(dev)
dev.set_configuration()
return 0
is run, I get:
1
0,0
129
1
Traceback (most recent call last):
File "test_pyusb.py", line 58, in <module>
sys.exit(main(sys.argv))
File "test_pyusb.py", line 52, in main
dev.set_configuration()
File "/usr/lib64/python2.7/site-packages/usb/core.py", line 819, in set_configuration
self._ctx.managed_set_configuration(self, configuration)
File "/usr/lib64/python2.7/site-packages/usb/core.py", line 129, in managed_set_configuration
self.backend.set_configuration(self.handle, cfg.bConfigurationValue)
File "/usr/lib64/python2.7/site-packages/usb/backend/libusb1.py", line 786, in set_configuration
_check(self.lib.libusb_set_configuration(dev_handle.handle, config_value))
File "/usr/lib64/python2.7/site-packages/usb/backend/libusb1.py", line 592, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno None] Other error
Note that the output says "Other error", not Unknown error - of which I found
several references.
When tested with a minimalistic C program, also with libusb 1.0.20, the transfer
actually starts, but stops after a couple of 512 data blocks.
Questions:
- In C, I have code that detaches the kernel driver if necessary. Is this necessary
here? I didn't find any reference in the tutorial.
- Any other tests I can do?
The system is Linux, kernel 4.1.6, Slackware 14.1, and libusb 1.0.20.
This is the lsusb -v output for the device:
Bus 001 Device 014: ID 1cbe:0003 Luminary Micro Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1cbe Luminary Micro Inc.
idProduct 0x0003
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 5
bmAttributes 0xc0
Self Powered
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 4
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0003
Self Powered
Remote Wakeup Enabled
|
|
From: Tormod V. <lis...@gm...> - 2016-02-16 08:04:14
|
On Tue, Feb 16, 2016 at 8:37 AM, <iov...@gm...> wrote: > Dear list members > > I am a very novice and inexperienced user and I apologize in advance for > what may seem an abomination in the land of python and serial interfaces. > > I need to drive a USB device (valve controller) which is operated by > d2xx type ftdi driver. > > I installed python 2.6 and original PyUSB module > http://bleyer.org/pyusb/ > > is it the same PyUSB that is discussed here? No, that is not pyusb as we know it here, which is at http://walac.github.io/pyusb/ "PyUSB aims to be an easy to use Python module to access USB devices. PyUSB relies on a native system library for USB access." I really can't understand why those other guys call their FTDI-specific library "pyusb"! Regards, Tormod |
|
From: Xiaofan C. <xia...@gm...> - 2016-02-16 07:57:03
|
On Tue, Feb 16, 2016 at 3:37 PM, <iov...@gm...> wrote: > Dear list members > > I am a very novice and inexperienced user and I apologize in advance for > what may seem an abomination in the land of python and serial interfaces. > > I need to drive a USB device (valve controller) which is operated by > d2xx type ftdi driver. > > I installed python 2.6 and original PyUSB module > http://bleyer.org/pyusb/ > > is it the same PyUSB that is discussed here? No. This pyusb is for Python binding of libusb-0.1, libusb-1.0 and OpenUSB. https://github.com/walac/pyusb I think that PyUSB for D2XX is no longer supported by its author and you'd better to switch to other versions. Maybe this one? https://github.com/snmishra/ftd2xx Or you can forget about d2xx and use pylibftdi or pyftdi. https://bitbucket.org/codedstructure/pylibftdi https://github.com/eblot/pyftdi -- Xiaofan |
|
From: <iov...@gm...> - 2016-02-16 07:37:19
|
Dear list members I am a very novice and inexperienced user and I apologize in advance for what may seem an abomination in the land of python and serial interfaces. I need to drive a USB device (valve controller) which is operated by d2xx type ftdi driver. I installed python 2.6 and original PyUSB module http://bleyer.org/pyusb/ is it the same PyUSB that is discussed here? I ran an original short test script # import the PyUSB module import d2xx # list devices by description, returns tuple of attached devices description strings d = d2xx.listDevices(d2xx.OPEN_BY_DESCRIPTION) print d # list devices by serial, returns tuple of attached devices serial strings d = d2xx.listDevices() # implicit d2xx.OPEN_BY_SERIAL_NUMBER print d h = d2xx.open(0) print h # read eeprom print h.eeRead() # get queue status print h.getQueueStatus() # set RX/TX timeouts h.setTimeouts(1000,1000) # write bytes (serial mode) print h.write('Hello world!\r\n") # read bytes (serial mode) print h.read(5) it seems that my device is visible and here is the output IDLE 2.6 >>> ================================ RESTART ================================ >>> ('ValveLink8.2',) ('FTT6NW6D',) <FtobjType object at 0x01E8D160> {'useExtOsc': 68, 'ifAIsFifoTar7': 0, 'powerSaveEnable': 149, 'ifBIsFastSer7': 2, 'maxPower': 0, 'bSlowSlew': 0, 'invertTXD': 202, 'manufacturerId': 'FT', 'signature1': 0, 'signature2': -1, 'invertRI': 248, 'cSlowSlew': 1, 'ahSchmittInput': 3, 'dSchmittInput': 0, 'bRIIsTXDEN': 0, 'dIsVCP8': 2, 'ahDriveCurrent': 1, 'vendorId': 1027, 'invertDCD': 2, 'highDriveIOs': 59, 'usbVersionEnable': 1, 'pullDownEnableR': 30, 'endpointSize': 3, 'aRIIsTXDEN': 0, 'invertDSR': 18, 'cRIIsTXDEN': 0, 'bhSlowSlew': 253, 'alSchmittInput': 39, 'version': 2, 'serNumEnableR': 224, 'cSchmittInput': 30, 'ifBIsFastSer': 0, 'usbVersion': 512, 'serNumEnable5': 0, 'isoOut': 0, 'dDriveCurrent': 0, 'invertRTS': 2, 'serNumEnable8': 2, 'manufacturer': 'AutoMate Scientific', 'cDriveCurrent': 1, 'bDriveCurrent': 3, 'cIsVCP8': 19, 'rIsD2XX': 68, 'ifAIsFifoTar': 0, 'serNumEnable7': 176, 'remoteWakeup': 0, 'bhDriveCurrent': 0, 'cbus0': 23, 'cbus1': 253, 'cbus2': 1, 'cbus3': 232, 'cbus4': 45, 'bIsVCP8': 167, 'alSlowSlew': 245, 'ifAIsFastSer7': 0, 'usbVersion5': 0, 'isoInA': 199, 'isoInB': 18, 'aDriveCurrent': 39, 'bIsVCP7': 180, 'ifAIsFifo': 0, 'bIsVCP': 0, 'selfPowered': 1, 'pnp': 1, 'ahSlowSlew': 51, 'invertCTS': 40, 'alDriveCurrent': 0, 'pullDownEnable': 0, 'bhSchmittInput': 1, 'aSlowSlew': 200, 'invertDTR': 199, 'serNumEnable': 1, 'aIsHighCurrent': 0, 'pullDownEnable8': 133, 'pullDownEnable7': 0, 'pullDownEnable5': 0, 'blDriveCurrent': 23, 'ifAIsFastSer': 0, 'aIsVCP7': 48, 'bSchmittInput': 51, 'ifBIsFifo7': 167, 'aIsVCP8': 48, 'ifBIsFifo': 0, 'isoIn': 0, 'usbVersionEnable5': 0, 'dRIIsTXDEN': 0, 'productId': 54872, 'invertRXD': 133, 'description': 'ValveLink8.2', 'dSlowSlew': 0, 'bIsHighCurrent': 0, 'ifAIsFifo7': 0, 'aIsVCP': 0, 'blSchmittInput': 248, 'rev5': 0, 'ifBIsFifoTar7': 19, 'serialNumber': 'FTT6NW6D', 'blSlowSlew': 30, 'aSchmittInput': 245, 'isoOutA': 2, 'isoOutB': 248, 'ifBIsFifoTar': 0, 'rev4': 1 I also know the control chars that need to be sent to device to open and close the valves "\nFv\r" <- toggle valve v, so \nF1\r toggles valve 1 "\nC\r" <- gives the details on the valvelink system, such as the controller address "\nI\r" <- Turns off all valves I modified the script to have print h.write("\nF2\r") but nothing happens – the valves do not respond any help would be vastly appreciated Thanks!! Iov |
|
From: Wander L. C. <wan...@gm...> - 2016-02-11 14:37:20
|
Hello there, First release candidate of PyUSB 1.0 is released. If no serious bug is found in the next 60 days, stable version will finally be released. -- Best Regards, Wander Lairson Costa |
|
From: Jay N. <ja...@ne...> - 2016-02-03 13:28:17
|
I have downloaded the files and installed them. I do not have any issues initially using it for my program (Zebra KR403 status program) but I will report any issues I find. Jay From: chris clark [mailto:cl...@gm...] Sent: Tuesday, February 02, 2016 12:13 To: pyu...@li... Subject: Re: [pyusb-users] [Release Candidate] Call for help If you are not familiar with git, you can also download a zip of the latest code from https://github.com/walac/pyusb/archive/master.zip On Tue, Feb 2, 2016 at 9:08 AM, Wander Lairson Costa <wan...@gm...> wrote: Just clone it from github 2016-02-02 13:41 GMT-02:00 Jay Newens <ja...@ne...>: > Where can I get the files for this release candidate to test with my system? > > Jay > > -----Original Message----- > From: Wander Lairson Costa [mailto:wan...@gm...] > Sent: Saturday, January 30, 2016 06:27 > To: pyusb-users > Subject: [pyusb-users] [Release Candidate] Call for help > > Hi there, > > I was about to release the first release candidate, but just found out > my test board died. As I don't know when/if I can recover it, could > you please guys clone the latest code and report if everything works > with your apps? > > Thanks a lot! > > -- > Best Regards, > Wander Lairson Costa > > ---------------------------------------------------------------------------- > -- > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311 <http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140> &iu=/4140 > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311 <http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140> &iu=/4140 > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users -- Best Regards, Wander Lairson Costa ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311 <http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140> &iu=/4140 _______________________________________________ pyusb-users mailing list pyu...@li... https://lists.sourceforge.net/lists/listinfo/pyusb-users |
|
From: chris c. <cl...@gm...> - 2016-02-02 18:13:20
|
If you are not familiar with git, you can also download a zip of the latest code from https://github.com/walac/pyusb/archive/master.zip On Tue, Feb 2, 2016 at 9:08 AM, Wander Lairson Costa < wan...@gm...> wrote: > Just clone it from github > > 2016-02-02 13:41 GMT-02:00 Jay Newens <ja...@ne...>: > > Where can I get the files for this release candidate to test with my > system? > > > > Jay > > > > -----Original Message----- > > From: Wander Lairson Costa [mailto:wan...@gm...] > > Sent: Saturday, January 30, 2016 06:27 > > To: pyusb-users > > Subject: [pyusb-users] [Release Candidate] Call for help > > > > Hi there, > > > > I was about to release the first release candidate, but just found out > > my test board died. As I don't know when/if I can recover it, could > > you please guys clone the latest code and report if everything works > > with your apps? > > > > Thanks a lot! > > > > -- > > Best Regards, > > Wander Lairson Costa > > > > > ---------------------------------------------------------------------------- > > -- > > Site24x7 APM Insight: Get Deep Visibility into Application Performance > > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > > Monitor end-to-end web transactions and take corrective actions now > > Troubleshoot faster and improve end-user experience. Signup Now! > > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > > _______________________________________________ > > pyusb-users mailing list > > pyu...@li... > > https://lists.sourceforge.net/lists/listinfo/pyusb-users > > > > > > > ------------------------------------------------------------------------------ > > Site24x7 APM Insight: Get Deep Visibility into Application Performance > > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > > Monitor end-to-end web transactions and take corrective actions now > > Troubleshoot faster and improve end-user experience. Signup Now! > > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > > _______________________________________________ > > pyusb-users mailing list > > pyu...@li... > > https://lists.sourceforge.net/lists/listinfo/pyusb-users > > > > -- > Best Regards, > Wander Lairson Costa > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users > |
|
From: Wander L. C. <wan...@gm...> - 2016-02-02 17:08:49
|
Just clone it from github 2016-02-02 13:41 GMT-02:00 Jay Newens <ja...@ne...>: > Where can I get the files for this release candidate to test with my system? > > Jay > > -----Original Message----- > From: Wander Lairson Costa [mailto:wan...@gm...] > Sent: Saturday, January 30, 2016 06:27 > To: pyusb-users > Subject: [pyusb-users] [Release Candidate] Call for help > > Hi there, > > I was about to release the first release candidate, but just found out > my test board died. As I don't know when/if I can recover it, could > you please guys clone the latest code and report if everything works > with your apps? > > Thanks a lot! > > -- > Best Regards, > Wander Lairson Costa > > ---------------------------------------------------------------------------- > -- > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > _______________________________________________ > pyusb-users mailing list > pyu...@li... > https://lists.sourceforge.net/lists/listinfo/pyusb-users -- Best Regards, Wander Lairson Costa |
|
From: Jay N. <ja...@ne...> - 2016-02-02 16:01:34
|
Where can I get the files for this release candidate to test with my system? Jay -----Original Message----- From: Wander Lairson Costa [mailto:wan...@gm...] Sent: Saturday, January 30, 2016 06:27 To: pyusb-users Subject: [pyusb-users] [Release Candidate] Call for help Hi there, I was about to release the first release candidate, but just found out my test board died. As I don't know when/if I can recover it, could you please guys clone the latest code and report if everything works with your apps? Thanks a lot! -- Best Regards, Wander Lairson Costa ---------------------------------------------------------------------------- -- Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ pyusb-users mailing list pyu...@li... https://lists.sourceforge.net/lists/listinfo/pyusb-users |
|
From: chris c. <cl...@gm...> - 2016-01-30 20:20:45
|
On Sat, Jan 30, 2016 at 4:27 AM, Wander Lairson Costa < wan...@gm...> wrote: > I was about to release the first release candidate, but just found out > my test board died. As I don't know when/if I can recover it, could > you please guys clone the latest code and report if everything works > with your apps? > I've only got the one app (https://bitbucket.org/clach04/coldtears_clock) to test with (but I rely on it as my clock for my DVR) just pulled headsrevs from master and it seems to be working Not an exhaustive test but I need high up-times and will notice if there is a problem :-) |
|
From: Wander L. C. <wan...@gm...> - 2016-01-30 12:28:15
|
Hi there, I was about to release the first release candidate, but just found out my test board died. As I don't know when/if I can recover it, could you please guys clone the latest code and report if everything works with your apps? Thanks a lot! -- Best Regards, Wander Lairson Costa |
|
From: Nicolas P. <nic...@aa...> - 2016-01-28 12:53:48
|
Looks like I found the answer to my problem. On this page http://www.libusb.org/wiki/APIs, I've read : "libusb is not suited for HID class devices. While it is possible to use libusb with HID class devices it requires the original HID class driver to be replaced by a driver which supports libusb, and this leads to a quite poor user experience on any platform other than Linux. It is recommended to use HIDAPI <http://www.signal11.us/oss/hidapi/> instead. HIDAPI provides convenient cross-platform access to HID class devices and can do so without any kernel driver concerns across all supported platforms." Nicolas Le 28/01/2016 08:21, Nicolas Pinault a écrit : > Hi, > > I'm trying to use a USB device under Windows7x64. > The device is HID like with custom protocol. > The USB device is recognised by Windows as a HID device (without error > nor warning shown is device manager). > It works perfectly with a host running QNX OS. > > With PyUSB : > Discovery of the device is OK. > Configuration of the device seems to be OK. > Reading/writing the device fails. > > Here is the code I use : > > import usb.core > import usb.util > > class Test(object): > def __init__(self): > self.VendorId = 0x15A2 > self.ProductId = 0x0073 > self.dev = usb.core.find(idVendor=self.VendorId, > idProduct=self.ProductId) > if not self.dev : > raise ValueError("Device not found") > print self.dev > > self.dev.set_configuration() > > cfg = self.dev.get_active_configuration() > intf = cfg[(0,0)] > self.interface = cfg[(0,0)].bInterfaceNumber > > self.dev.set_interface_altsetting(interface = self.interface, > alternate_setting = self.interface) > > print "Interface :", self.interface > self.DeviceSetIdle() > > def DeviceSetIdle(self): > self.dev.ctrl_transfer(bmRequestType = > usb.util.build_request_type(usb.util.CTRL_OUT, > usb.util.CTRL_TYPE_CLASS, > usb.util.CTRL_RECIPIENT_INTERFACE), > bRequest = USB_HID_SET_IDLE_REQUEST, > # 0x0A > wValue = 0,#8 << 8, > wIndex = self.interface, > data_or_wLength = None, > timeout = 0) > > if __name__ == '__main__': > t = Test() > > I get the following output : > DEVICE ID 15a2:0073 on Bus 003 Address 023 ================= > bLength : 0x12 (18 bytes) > bDescriptorType : 0x1 Device > bcdUSB : 0x200 USB 2.0 > bDeviceClass : 0x0 Specified at interface > bDeviceSubClass : 0x0 > bDeviceProtocol : 0x0 > bMaxPacketSize0 : 0x40 (64 bytes) > idVendor : 0x15a2 > idProduct : 0x0073 > bcdDevice : 0x2 Device 0.02 > iManufacturer : 0x1 Freescale Semiconductor Inc. > iProduct : 0x2 Kinetis Bootloader > 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 : 0xc0 Self Powered > 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 : 0x40 (64 bytes) > bInterval : 0xa > ENDPOINT 0x2: Interrupt OUT ========================== > bLength : 0x7 (7 bytes) > bDescriptorType : 0x5 Endpoint > bEndpointAddress : 0x2 OUT > bmAttributes : 0x3 Interrupt > wMaxPacketSize : 0x40 (64 bytes) > bInterval : 0xa > Interface : 0 > Traceback (most recent call last): > File > "Z:\Cantar2\Processeur\Apps_2\PyCantarem2Update\src\PyCantarem2Update.py", > line 244, in <module> > t = Test() > File > "Z:\Cantar2\Processeur\Apps_2\PyCantarem2Update\src\PyCantarem2Update.py", > line 154, in __init__ > self.DeviceSetIdle() > File > "Z:\Cantar2\Processeur\Apps_2\PyCantarem2Update\src\PyCantarem2Update.py", > line 174, in DeviceSetIdle > timeout = 0) > File "C:\Python27\lib\site-packages\usb\core.py", line 1043, in > ctrl_transfer > self.__get_timeout(timeout)) > File "C:\Python27\lib\site-packages\usb\backend\libusb1.py", line > 883, in ctrl_transfer > timeout)) > File "C:\Python27\lib\site-packages\usb\backend\libusb1.py", line > 595, in _check > raise USBError(_strerror(ret), ret, _libusb_errno[ret]) > usb.core.USBError: [Errno 22] Invalid parameter > > As I am far from a USB ninja, I spent days documenting myself and > searching the Internet for a solution without success. > > What's wrong with my code ? > > 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 > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 > > > _______________________________________________ > 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 |
13 messages has been excluded from this view by a project administrator.
