On Sun, Apr 25, 2021 at 08:54:20PM +0300, Арам Абовян wrote:
> thanks for the previous answer. I also get the error.
>
>
> When I applied the following few lines in IDLE Python GUI:
>
> import usb.core
>
> dev = usb.core.find(idVendor=0x10c4, idProduct=0xea61)
> ep = dev[0].interfaces()[0].endp
thanks for the previous answer. I also get the error.
When I applied the following few lines in IDLE Python GUI:
import usb.core
dev = usb.core.find(idVendor=0x10c4, idProduct=0xea61)
ep = dev[0].interfaces()[0].endpoints()[0]
i = dev[0].interfaces()[0].bInterfaceNumber
dev.reset()
if dev.is_k
On Thu, Apr 22, 2021 at 01:38:58PM +0300, Арам Абовян wrote:
> -- Forwarded message -
> От: Aram Abovyan
> Date: чт, 22 апр. 2021 г., 13:37
> Subject:
> To: abovanara...@gmail.com
>
>
> I am very new to PyUSB and any help from PyUSB experts will be highly
> appreciated. .
>
> W
-- Forwarded message -
От: Aram Abovyan
Date: чт, 22 апр. 2021 г., 13:37
Subject:
To: abovanara...@gmail.com
I am very new to PyUSB and any help from PyUSB experts will be highly
appreciated. .
When I applied the following few lines in IDLE Python GUI,
-
FYI as well.
-- Forwarded message -
From: Chris Dickens
Date: Fri, Dec 11, 2020 at 5:11 PM
Subject: [libusb] Announcing libusb v1.0.24
To: libusb-devel
Hi,
I am pleased to announce the libusb-1.0.24 final release.
This release has been long awaited, with 185 commits going in o
Hey Gerry,
I think I found the problem. In your Python configuration, you
set_configuration and then reset the device. Besides the fact the device
looses the configuration information, this will cause a reenumeration, and
the device driver will be attached again. Try to comment the dev.reset line
Hi Gerry,
I didn't forget you, but I didn't find free time yet to look deep at your
code, sorry.
2015-01-20 9:24 GMT-02:00 Gerry :
> Sorry for the late reply but I had sent this to the pyusb-users-owner
> list instead of this list. I had originally included the files as
> attachments but the l
Sorry for the late reply but I had sent this to the pyusb-users-owner
list instead of this list. I had originally included the files as
attachments but the list stripped them off so now I am including them in
this email.
Hopefully someone can find a solution to this problem.
Forwar
This message was sent earlier but it never showed up on the mail list.
In fact there are no mails showing up from Jan 1 - Jan 11, 2015...
All of the errors that show up in PyUSB happen in the PyUSB.core file
when I try to read from a device.
Forwarded Message
Subject:
Hi Karl,
Those are the numbers they gave me. Do you think converting the vendor ID
to hex (or product ID to decimal) could fix the problem?
Thanks,
Irina
On Fri, May 3, 2013 at 3:40 PM, Karl P wrote:
>
>
> On 05/03/2013 06:48 PM, Wander Lairson Costa wrote:
> > 2013/5/3 I Rabkina :
> >> Hello
Hi Wander,
I am using Mac OS X with Python 2.7.
Thanks,
Irina
On Fri, May 3, 2013 at 11:48 AM, Wander Lairson Costa <
wander.lair...@gmail.com> wrote:
> 2013/5/3 I Rabkina :
> > Hello,
> >
> > I am just getting started with pyusb. I need it to send an high/low
> signal
> > to a DAQ box using U
On 05/03/2013 06:48 PM, Wander Lairson Costa wrote:
> 2013/5/3 I Rabkina :
>> Hello,
>>
>> I am just getting started with pyusb. I need it to send an high/low signal
>> to a DAQ box using USB. Unfortunately, I am coming across a problem within
>> the first few lines of code. Specifically, pyusb c
2013/5/3 I Rabkina :
> Hello,
>
> I am just getting started with pyusb. I need it to send an high/low signal
> to a DAQ box using USB. Unfortunately, I am coming across a problem within
> the first few lines of code. Specifically, pyusb can't find the device. I
> assumed that the error was from hav
Hello,
I am just getting started with pyusb. I need it to send an high/low signal
to a DAQ box using USB. Unfortunately, I am coming across a problem within
the first few lines of code. Specifically, pyusb can't find the device. I
assumed that the error was from having incorrect IDs, but I've chec
Hi,
Thanks for your support. I will try it out.
Best Regards,
Rinu
On Mon, Feb 20, 2012 at 7:11 PM, Wander Lairson Costa <
wander.lair...@gmail.com> wrote:
> 2012/2/20 Rinu Cleetus :
> > Hi All,
> >
> > I am trying to install pyusb-1.0.0a2 with python 2.4.4. I downloaded the
> > pyusb from
> >
2012/2/20 Rinu Cleetus :
> Hi All,
>
> I am trying to install pyusb-1.0.0a2 with python 2.4.4. I downloaded the
> pyusb from
> http://space.dl.sourceforge.net/project/pyusb/PyUSB%201.0/1.0.0-alpha-2/pyusb-1.0.0a2.zip
> It says that it supports python version >=2.4.
>
> While installing I get the er
Hi All,
I am trying to install pyusb-1.0.0a2 with python 2.4.4. I downloaded the
pyusb from
http://space.dl.sourceforge.net/project/pyusb/PyUSB%201.0/1.0.0-alpha-2/pyusb-1.0.0a2.zip
It says that it supports python version >=2.4.
While installing I get the error:
byte-compiling C:\Python24\Lib\si
On Sat, Feb 18, 2012 at 11:29 AM, Yunong Pang <029...@gmail.com> wrote:
> en... What I means is ,read() runs well in bulkloop, but not in reading
> camera.
>
The thing is that the camera may need some command to
be put in the mode to accept read command.
You have to know the device protocol in or
en... What I means is ,read() runs well in bulkloop, but not in reading
camera.
On Sat, Feb 18, 2012 at 8:19 AM, Xiaofan Chen wrote:
> On Sat, Feb 18, 2012 at 12:18 AM, Yunong Pang <029...@gmail.com> wrote:
> > When I test the read() in bulkloop program, it can read the
> > data successfully.
>
On Sat, Feb 18, 2012 at 12:18 AM, Yunong Pang <029...@gmail.com> wrote:
> When I test the read() in bulkloop program, it can read the
> data successfully.
> I don't know how to test it now...
For bulkloop, you send something first to OUT endpoint
EP2OUT and then you read from the IN endpoint EP6IN
2012/2/17 Yunong Pang <029...@gmail.com>:
> The result remains the same to not import libusb01.
>
> How can I test that there is data really staying in EP6 ?
>
>
I don't know how to do this, as data is requested on demand. There is
no buffering is USB. Have you tried to apply a larger timeout valu
The result remains the same to not import libusb01.
How can I test that there is data really staying in EP6 ?
>>> from usb.backend import libusb01
>>> b = libusb01.get_backend()
>>> dev = usb.core.find(idVendor=0x0547, idProduct=0x1002, backend = b)
>>> dev.set_configuration()
>>> ret = dev.re
2012/2/17 Yunong Pang <029...@gmail.com>:
> I grep out two results...
> $ rpm -qa | grep libusb
>
> libusb1-1.0.8-1.fc14.i686
> libusb-0.1.12-23.fc14.i686
>
> I don't know which one is my libusb version.
>
The first one. But you also have the libusb 0.1. Let's try to force
its use and check if we
When I test the read() in bulkloop program, it can read the
data successfully.
I don't know how to test it now...
On Sat, Feb 18, 2012 at 12:10 AM, Yunong Pang <029...@gmail.com> wrote:
> I grep out two results...
> $ rpm -qa | grep libusb
>
> libusb1-1.0.8-1.fc14.i686
> libusb-0.1.12-23.fc14.i
I grep out two results...
$ rpm -qa | grep libusb
libusb1-1.0.8-1.fc14.i686
libusb-0.1.12-23.fc14.i686
I don't know which one is my libusb version.
On Sat, Feb 18, 2012 at 12:03 AM, Wander Lairson Costa <
wander.lair...@gmail.com> wrote:
> 2012/2/17 Yunong Pang <029...@gmail.com>:
> > Bus 002 D
2012/2/17 Yunong Pang <029...@gmail.com>:
> Bus 002 Device 018: ID 0547:1002 Anchor Chips, Inc. Python2 WDM Encoder
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 0 (Defined at Interface level)
> bDeviceSu
Bus 002 Device 018: ID 0547:1002 Anchor Chips, Inc. Python2 WDM Encoder
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacke
2012/2/17 Yunong Pang <029...@gmail.com>:
>
> OS: Fedora 14 (2.6.35.10-74.fc14.i686)
>
>
> Info from DEBUG
dev.read(0x86, 1024, 0, 100)
> 2012-02-17 23:34:41,768
> DEBUG:usb.backend.libusb10:_LibUSB.get_configuration_descriptor( object at 0x99fffec>, 0)
> 2012-02-17 23:34:41,769
> DEBUG:usb.
OS: Fedora 14 (2.6.35.10-74.fc14.i686)
Info from DEBUG
>>> dev.read(0x86, 1024, 0, 100)
2012-02-17 23:34:41,768
DEBUG:usb.backend.libusb10:_LibUSB.get_configuration_descriptor(, 0)
2012-02-17 23:34:41,769
DEBUG:usb.backend.libusb10:_LibUSB.get_interface_descriptor(, 0, 0, 0)
2012-02-17 23:34:41
2012/2/17 Yunong Pang <029...@gmail.com>:
> Hi all,
>
> I'm writing some code to get data from camera module ov7670.
>
> I can see the data has been output from the module, as the waveform has
> changed when putting different image before the camera. And the EP6, which
> is set to be AUTOIN , is fu
Dear all,
Emmanuel Blot has registered PyUSB 1.0.0a1 in PyPi, thus you can
install PyUSB through easy_install.
Thank you very much, Emmanuel.
-- Forwarded message --
From: Emmanuel Blot
Date: 2011/3/15
Subject: Re: [pyusb-users] Pypi update for pyusb
To: "wander.lairson"
>>
Just to let you know, I've send this email to the libusb mailing list.
-- Forwarded message --
From: David Portabella Clotet
Date: Fri, Feb 6, 2009 at 11:14 PM
Subject: libusb-win32 & pyusb-0.4.1 for cygwin
To: libusb-win32-de...@lists.sourceforge.net
Hello,
I am having problem
32 matches
Mail list logo
