On Mon, Apr 5, 2010 at 8:21 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Mon, Apr 5, 2010 at 6:42 PM, Wander Lairson wander.lair...@gmail.com
wrote:
Please, try to find the device from python prompt, just do it:
import usb.core
dev = usb.core.find(idVendor=0xFFFE)
assert dev is not None
On Tue, Apr 6, 2010 at 9:26 PM, Wander Lairson wander.lair...@gmail.com wrote:
I added some preliminary log support to PyUSB at revision 56, it uses
the logging module. Currently, you can define the environment variable
PYUSB_DEBUG_LEVEL with the following values: critical, error, warning,
On Thu, Apr 8, 2010 at 7:37 AM, Wander Lairson wander.lair...@gmail.com wrote:
with libusb 1.0 built with Visual C++, it is hanging during the tests:
C:\Projetos\pyusb\trunkcd tests
C:\Projetos\pyusb\trunk\testspython testall.py
2010-04-07 20:26:02,765
On Thu, Apr 8, 2010 at 8:08 AM, Wander Lairson wander.lair...@gmail.com wrote:
I tried to manually interact with device using python command prompt,
and it worked fine:
C:\Projetos\pyusb\trunkpython
ActivePython 2.6.1.1 (ActiveState Software Inc.) based on
Python 2.6.1 (r261:67515, Dec 5
On Thu, Apr 8, 2010 at 10:01 PM, Xiaofan Chen xiaof...@gmail.com wrote:
Ah, this may be the case. I need to ask again in the libusb mailing
list. The MSVC solution generates stdcall. And I believe if they
are different, then Pete will need to change the MinGW/Cygwin
build to use stdcall
On Tue, Apr 13, 2010 at 2:15 AM, Wander Lairson
wander.lair...@gmail.com wrote:
Hello,
I think last error was caused by the device not being successfully
reenumerated after failed call to device_reset function.
I tried to look at libusb 1.0 source code (http://libusb.org/browser),
but I
On Wed, Apr 14, 2010 at 10:24 PM, Wander Lairson
wander.lair...@gmail.com wrote:
Deeper investigation showed that it is caused by calling
set_configuration twice when device is connected. Example:
import usb.core
d = usb.core.find(idVendor=0xfffe)
d.set_configuration()
d.write(1,
On Thu, Apr 15, 2010 at 6:54 AM, Wander Lairson
wander.lair...@gmail.com wrote:
And there are quite often problem like this: first run works and
then 2nd run got time out. Typically the issue only happens
under Linux. It is mostly related to set_interface command response.
In this case, it
On Fri, Apr 16, 2010 at 11:14 PM, Wander Lairson
wander.lair...@gmail.com wrote:
Known issues
-
- 'reset' method fails under FreeUSB (libusb 1.0 backend).
'reset' method fails under FreeUSB 8.0 (libusb 1.0 backend). I am
not so sure about the older system.
One more: libusb
On Mon, Apr 19, 2010 at 5:07 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Mon, Apr 19, 2010 at 7:57 AM, Xiaofan Chen xiaof...@gmail.com wrote:
I said that the 0.4.2 example works in the legacy mode. But it is
using the 1.0 backend as you mentioned.
How do I force usb.legacy to use
On Mon, Apr 19, 2010 at 5:22 PM, Xiaofan Chen xiaof...@gmail.com wrote:
As a test, I delete pyusb 1.0 and then install pyusb-0.4.2. It does
seem to work.
The following is a simple test program for Microchip PICkit 2. It
does seem to work.
#!/usr/bin/env python
import usb
def opendevice
On Mon, Apr 26, 2010 at 12:25 AM, Kevin Kilroy kevkil...@googlemail.com wrote:
Hi all,
I'm having difficulty getting pyusb to find my HID usb device, here are the
steps I have taken so far:
Download install pyusb-1.0.0-a0 (by unpacking excuting python setup.py
install from within cygwin)
On Mon, Apr 26, 2010 at 7:43 AM, Xiaofan Chen xiaof...@gmail.com wrote:
When I tested pyusb with Cygwin, I build libusb-1.0 within
Cygwn and not using the snapshots. It seems to me Cygwin
is looking for cyusb-1.0.dll and not libusb-1.0.dll.
You may want to try this out.
Or you can use
On Mon, Apr 26, 2010 at 7:43 AM, Xiaofan Chen xiaof...@gmail.com wrote:
When I tested pyusb with Cygwin, I build libusb-1.0 within
Cygwn and not using the snapshots. It seems to me Cygwin
is looking for cyusb-1.0.dll and not libusb-1.0.dll.
It works for me. Here is the log with an HID
On Thu, Apr 22, 2010 at 6:23 PM, Loïc GRENON dif...@tuxfamily.org wrote:
Hi,
I'm currently developing a python application to communicate with an USB
device, with pyusb (that use libusb).
Communications are through control request.
The program works very well on a computer running Fedora
On Thu, Apr 22, 2010 at 6:55 PM, Loïc GRENON dif...@tuxfamily.org wrote:
Nom : pyusb
Architecture : x86_64
Version : 0.4.1
Révision : 5.fc12
Taille : 41 k
Could you try the latest version of pyusb 0.4.3? It might help.
When I tried pyusb under Ubuntu 64, it
On Sat, May 29, 2010 at 4:35 AM, Mark m...@absamail.co.za wrote:
I'll try to install the filter package. I seem to recall reading about
not installing the filter version because it was 'broken'. I did create
an .inf for my device XP does load the driver when I attach my device.
When I look in
On Sun, May 30, 2010 at 11:31 PM, Karl Palsson tw...@tweak.net.au wrote:
If you're screwing around with inf files, (in my opinion) you're doing it
wrong.
I (finally) got windows XPand ubuntu working with (almost) the same code, and
no
inf files.
On Mon, May 31, 2010 at 4:53 PM, juerg maier juerg.ma...@jmid.ch wrote:
Hi
downloaded pyusb-0.4.3.win32-py2.6.exe and ran it (W7/64).
It found my Python 2.6 installation and extracted it
into F:\Python26\Lib\site-packages
Created a new Exclipse Pyton26 project and tried to follow the example
On Mon, May 31, 2010 at 6:58 PM, juerg maier juerg.ma...@jmid.ch wrote:
Hi Xiaofan
Thanks for your reply. Made also a try for d2xx (PyUSB-1.6.win32-py2.6) but
it throws an error on the import d2xx line.
Downloaded also PIL module for working with images and this worked perfectly
in my
On Wed, Jun 2, 2010 at 11:56 PM, Ct Chev ctc.1...@yahoo.com wrote:
and I get the following error:
Traceback (most recent call last):
File usbenum.py, line 46, in module
handle.interruptWrite(2, *IDN?\n)
usb.USBError: Unknown error
Output from usbenum.py:
Device: /dev/ugen2.3
So are you
On Thu, Jun 3, 2010 at 9:14 AM, Xiaofan Chen xiaof...@gmail.com wrote:
So are you using FreeBSD? Which version of FreeBSD are you using?
From my experience, libusb under FreeBSD 6/7 is basically not really
that usable unless you try the alternative HPS USB stack.
Please refer to my old
On Thu, Jun 3, 2010 at 8:49 PM, Ct Chev ctc.1...@yahoo.com wrote:
Thank you for the feedback everyone!
I am using FreeBSD 8,
8-Release or 8-Stable? The default 8-release (even with the updates)
comes with a buggy libusb.
Try this (this is also not the latest).
On Thu, Jun 17, 2010 at 9:45 PM, Alex alex.kronenw...@gmx.de wrote:
Hi together,
I'm trying to communicate with a RIU (reconfigurable Interface unit) but
I'm facing a problem which I can't solve.
I am using Windows XP, python 2.5 and libusb 1.0.
I think you mean libusb-win32, right?
On Fri, Jun 18, 2010 at 1:45 PM, alex.kronenw...@gmx.de wrote:
You're right, it's libusb-win32, the version is
libusb-win32-device-bin-20100519.
You probably want to use the release version instead of a snapshot version.
But that is not a big problem.
The RIU should respond either with good
On Thu, Jun 24, 2010 at 8:15 AM, Diego Jacobi jacobidi...@gmail.com wrote:
But what i need from this device is to be able to use it through a
userspace software with USB. This is not yet the problem, because i
could in last instance, use the virtual serial port, but it requires
special
On Thu, Jun 24, 2010 at 9:08 AM, Diego Jacobi jacobidi...@gmail.com wrote:
There is a driver in the kernel for sure.
Could you please expand your answer on this?
How do i detach a driver from the kernel in user space?
For libusb-0.1
On Thu, Jun 24, 2010 at 12:25 PM, Diego Jacobi jacobidi...@gmail.com wrote:
Can somebody give a better example on how to call ctrl_transfer with a
data payload ?
It all depends on the device.
A C example here (sorry right now I have no pyusb example).
On Fri, Jun 25, 2010 at 1:44 AM, Diego Jacobi jacobidi...@gmail.com wrote:
I cant get ctrol_transfer to work in anyway. It will always give an error.
Calling it even without payload:
I readed all of the pertinent source code of pyusb until the call to
libusb, and I myself cant find what the
On Mon, Jun 28, 2010 at 1:58 AM, Diego Jacobi jacobidi...@gmail.com wrote:
I programmed on the device a couple of Vendor requests so i know for
sure what does it answers.
I also programmed the comunication in C with libusb 1.0 and with pyusb.
PyUSB gives different error messages (always -1
On Sat, Jul 10, 2010 at 12:12 AM, Wander Lairson
wander.lair...@gmail.com wrote:
The problem was in a CopyPaste error where i have defined the
endpoint numbers as:
TI_EP_BULK_UART1_OUT = 0x01
TI_EP_BULK_UART1_OUT = 0x81
And they should be:
TI_EP_BULK_UART1_OUT = 0x01
TI_EP_BULK_UART1_IN
On Mon, Jul 12, 2010 at 10:15 PM, Wander Lairson
wander.lair...@gmail.com wrote:
As much more people use libusb instead of OpenUSB (probably because
OpenUSB is an younger library), I postponed it in favor of making the
libusb backend stable. I hope getting libusb reasonably stable and
start
On Thu, Jul 15, 2010 at 2:57 AM, John Harrison
johnharrison...@gmail.com wrote:
If so, which libusb do you recommend I install for win32? I looked at
libusb-win32:
http://sourceforge.net/apps/trac/libusb-win32/wiki
and I assume I install the device driver from that?
The usb component I am
On Thu, Jul 15, 2010 at 3:25 AM, Wander Lairson
wander.lair...@gmail.com wrote:
You can install libusb device driver either as a filter driver or as
the device driver for your component. If you choose the former, I
guess you don't need to uninstall your current driver (but probably
will be
On Fri, Jul 16, 2010 at 2:12 AM, Wander Lairson
wander.lair...@gmail.com wrote:
2010/7/15 John Harrison johnharrison...@gmail.com:
libusb-win32-bin-1.2.0.0\bin\x86testlibusb.exe
Dev #0: -
Dev #2: Measurement Computing - USB-2001-TC
Dev #2 is the correct name for my device.
Oh,
On Tue, Jul 27, 2010 at 8:24 AM, Qui Le q...@extron.com wrote:
So far after a lot of test runs, I realize that my device works only works
with 1.1.14.3 and never works under 1.2.0.0
I ran the testbulk.exe provided from the libusb-win32 sources with
modifications in the code to match with my
On Tue, Jul 27, 2010 at 9:05 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Jul 27, 2010 at 8:24 AM, Qui Le q...@extron.com wrote:
So far after a lot of test runs, I realize that my device works only works
with 1.1.14.3 and never works under 1.2.0.0
Please post this to the libusb-win32
On Tue, Jul 27, 2010 at 9:20 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Jul 27, 2010 at 9:05 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Tue, Jul 27, 2010 at 8:24 AM, Qui Le q...@extron.com wrote:
So far after a lot of test runs, I realize that my device works only works
On Mon, Aug 23, 2010 at 12:59 PM, Max Teo max...@gmail.com wrote:
Hi,
In case I had missed out the previous forum msgs, just wanted to ask why
there's no backend available when using
libusb10 as the backend.
Using zadig as the tool to get the correct drivers installed for XP, the
On Tue, Aug 24, 2010 at 1:54 PM, Max Teo max...@gmail.com wrote:
Another question related to this, I was able to send a mass storage
command using ATA16 passthru.
The first command succeeded however the second similar command got back a
Pipe Error.
...
File stdin, line 1, in module
On Tue, Aug 24, 2010 at 5:13 PM, Max Teo max...@gmail.com wrote:
ind.read(13, timeout=5000)
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [libusb_get_config_descriptor] index 0
libusb:debug [winusb_submit_bulk_transfer] matched endpoint 81 with
interface 0
libusb:debug
On Wed, Sep 8, 2010 at 7:49 AM, Massimo Di Stefano
massimodisa...@gmail.com wrote:
Hello All,
i'm tring to learn pyusb, i'm on a mac osx 10.6.4
i buid libusb from source with log enabled
googling i tried learn how to read data from an USB device (a joystick)
i find this code :
import usb
On Sun, Oct 10, 2010 at 12:55 PM, Ladislav Szolik
szolik.ladis...@gmail.com wrote:
ok, thats fine. Thank you for your answer. The main point of a school
project is communication with real system, which is plugged to pc via USB
cable. And the client can this system regulate. So there will be
On Tue, Nov 23, 2010 at 12:33 PM, Andrew Errington
a.erring...@lancaster.ac.uk wrote:
Hello everyone,
I have had some success with PyUSB, but it's all new to me and I am struggling
with something which should be simple. I am using PyUSB v1.0.
I am trying to write to the GPIO pins on a USB
On Tue, Nov 23, 2010 at 12:33 PM, Andrew Errington
a.erring...@lancaster.ac.uk wrote:
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass
On Wed, Jan 5, 2011 at 3:19 AM, Emmanuel Blot eblot...@gmail.com wrote:
Anyway, you have to install the device driver for your peripheral.
This is what I did: I've installed the D2XX Windows drivers (latest
release) available from the FTDI web site.
My understanding is that for libusb-1.0 at
On Wed, Jan 5, 2011 at 5:21 PM, wander.lairson wander.lair...@gmail.com wrote:
Cygwin is still unsupported. I've given just a shallow look on Cygwin,
but it feels like it just has the static versions of libusb 1.0 and
libusb-win32.
Once upon a time, I got Cygwin to work with pyusb and
On Wed, Jan 5, 2011 at 10:45 PM, Emmanuel Blot eblot...@gmail.com wrote:
I've copied
\libusb_2010.12.10\MS64\dll\libusb-1.0.dll into System32, and
\libusb_2010.12.10\MS32\dll\libusb-1.0.dll into SystemWOW64.
Am I right or should I move the DLL elsewhere ?
This is correct.
I still get
On Wed, Mar 16, 2011 at 1:06 AM, wander.lairson
wander.lair...@gmail.com wrote:
This all works 'out of the box'. I don't have to detach any interfaces, and
the operation of the sound card is unaffected (other programs can use it
independently of this test code). If I give a user write
On Tue, Mar 15, 2011 at 10:55 PM, Emmanuel Blot eblot...@gmail.com wrote:
I need to detach *all* the interfaces from the (Linux) kernel, or I
sometime get an error (not a big deal for my use case)
I also need to call dev.set_configuration() to configure the device.
Nothing unusual I guess.
On Mon, Apr 11, 2011 at 12:44 AM, Robin Kluth commi1...@googlemail.com wrote:
Hello everyone,
I'll try to build a Python program under windows using PyUSB, Py2EXE etc..
My problem is: I dont get PyUSB working correctly. It should work with an
HID-USB Device (an Oregon Scientific WMRS200
On Tue, Apr 26, 2011 at 8:34 AM, Prashant Patel prash...@wipath.co.nz wrote:
Hi,
I am new to PyUSB and libusb-win32. I am trying to send data to my HID
device to turn LED ON/OFF along with some characters to display on LCD on
the Device. As my HID Device got the ready made code from Renesas
On Wed, Apr 27, 2011 at 9:06 AM, Prashant Patel prash...@wipath.co.nz wrote:
(3) The I come across the following post. Which said, I should download the
binary snapshots and put the DLL inside windows\system32 directory.
On Wed, Apr 27, 2011 at 9:06 AM, Prashant Patel prash...@wipath.co.nz wrote:
Hi Xiaofan,
Thank you for reply. I did test using SimpleHIDWrite and come to some
interesting observations:
(1) At first I tried SimpleHIDWrite and it was not detecting my device.
Then I uninstalled the driver from
On Wed, Apr 27, 2011 at 9:58 AM, Prashant Patel prash...@wipath.co.nz wrote:
libusb-1.0 Windows no longer support native HID backend.
I want to write and read to my HID Device from Python. It will be good if
you can suggest me, which Python USB API, I should use. As I have just
started my
On Wed, Apr 27, 2011 at 12:19 PM, Prashant Patel prash...@wipath.co.nz wrote:
Hi Xiaofan,
This is very very helpful. Finally I have found the LibUSB example for
Renesas Rx62N. So now I don't mind using custom driver. I don't see any
reason to stick with HID.
One thing, I will need, is to
On Sat, Jul 23, 2011 at 7:51 AM, Xiaofan Chen xiaof...@gmail.com wrote:
This pyusb mailing list is deal with the python binding for libusb.
http://sourceforge.net/projects/pyusb/
Your PyUSB is deal with python binding for FTDI's proprietary d2xx.
http://bleyer.org/pyusb/
So you might want
On Wed, Jul 27, 2011 at 3:28 AM, Bill Patterson
bpatter...@awarepoint.com wrote:
Thanks XiaoFan,
Can you forward me the tweaks? I still can't get it to compile, though not
a big VC++ user either!
Here it is. The modified archive and the 32bit Python 2.7 binary (msi format)
are inside.
On Sat, Jul 30, 2011 at 5:26 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, Jul 30, 2011 at 2:12 PM, C Duff duffman@gmail.com wrote:
Thanks Xiaofan,
I didn't know about the reset - I'll make sure to add that. And everything
now works.
The reset call is normally not necessary and I
LinkedIn
I'd like to add you to my professional network on LinkedIn.
- Xiaofan
Xiaofan Chen
Staff Engineer at Rockwell Automation
Singapore
Confirm that you know Xiaofan Chen
https://www.linkedin.com/e/tbchug-gr1w4892-4m/isd/3781283125/cADrLd-y/
--
(c) 2011, LinkedIn
On Mon, Aug 8, 2011 at 4:24 AM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
The reset issue is related to libusb 1.0 windows backend. Libusb guys
can give you better explanation on that (or maybe Xiaofan if he is
around here).
Yes I am around. :-)
libusb-1.0 Windows (currently use
2011/9/7 Cornelius Kölbel cornelius.koel...@lsexperts.de:
Hello Wander,
I just stumbled upon this thread.
http://www.mail-archive.com/pyusb-users@lists.sourceforge.net/msg00839.html
I am using pyusb and python-yubico to program yubikeys on linux and on
windows.
We realized that it will
On Wed, Nov 16, 2011 at 12:37 PM, Safoura s.seddig...@gmail.com wrote:
I don't have pyusb or python installed on the customer's mashines but
have installed libusb-win32.
If I run my exe python code by double clicking on it, it runs fine
(usb opened and read)
If my java code runs it, this
On Sun, Nov 27, 2011 at 8:54 AM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
As far as I know, libusb is problematic with HID devices, you should
take a look at hidapi [2], but I don't know if there is any python
binding for it.
[2] http://www.signal11.us/oss/hidapi/
Yes there is a
On Tue, Nov 29, 2011 at 12:41 AM, Safoura s.seddig...@gmail.com wrote:
Hi Ian,
I have an executable python that I call in my java code using java
runtime.exec. Therefore I don't need to install python or PyUSB on the
computers I run the software on.
Maybe that is not true and that is the
On Tue, Nov 29, 2011 at 12:06 PM, Safoura s.seddig...@gmail.com wrote:
Hello
Please see the links here:
Here is my code (partially):
http://pastebin.com/u/safoura
So the following line does not work, right?
p =
On Wed, Nov 30, 2011 at 1:11 AM, Barney, Bryson bbar...@sandia.gov wrote:
Hi,
I am new here, and a new user of PyUSB. I have a very simple HID
Isochronous application to use this for,
Take note HID is only using Interrupt Transfer. And Isochronous
transfer is not easy to deal with and I
On Sun, Dec 25, 2011 at 3:49 AM, Stephen Conley conle...@me.com wrote:
Hi - new to PyUSB and attempting to read GPS info from Garmin USB GPS. I am
using the Windows 7 (64 bit) and have installed libusb0. The Garmin driver
also appears to be connected to the GPS.
I get the error:
[Errno
On Sun, Dec 25, 2011 at 8:02 AM, Stephen Conley conle...@me.com wrote:
Here is the output:
I am using the filter - how do I use the device driver mode instead?
You use the GUI inf-wizard to install the device driver. Take note
that it will replace the existing driver.
What is the original
On Fri, Jan 20, 2012 at 12:02 AM, Peter Bigot
pabi...@users.sourceforge.net wrote:
From: Peter A. Bigot pabi...@users.sourceforge.net
With libusb-0.1.12-72 on openSUSE, the device bus number is encoded in the
dirname string, not in the location value. Validate this on a system that
uses the
On Fri, Jan 20, 2012 at 10:47 AM, Peter Bigot
pabi...@users.sourceforge.net wrote:
On Thu, Jan 19, 2012 at 7:24 PM, Xiaofan Chen xiaof...@gmail.com wrote:
On Fri, Jan 20, 2012 at 12:02 AM, Peter Bigot
pabi...@users.sourceforge.net wrote:
Is this libusb-0.1.12-72 the legacy libusb-0.1 version
On Sat, Jan 21, 2012 at 2:33 AM, Peter Bigot
pabi...@users.sourceforge.net wrote:
Could you please post your full test codes?
The only thing above that was import usb. That code does assume
that the backend is libusb01; if the error you're getting is:
AttributeError: '_Device' object has no
On Sat, Jan 21, 2012 at 9:17 PM, Peter Bigot
pabi...@users.sourceforge.net wrote:
On Sat, Jan 21, 2012 at 6:50 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sat, Jan 21, 2012 at 2:33 AM, Peter Bigot
pabi...@users.sourceforge.net wrote:
Could you please post your full test codes?
The only
I am not so sure why the libusb-0.1 backend can not enumerate the
device under Mac OS X Lion. Here libusb-compat-0.1 is used
and I built it as universal binary. libusb-1.0 backend works fine.
mymacmini:pyusb xiaofanc$ python
Python 2.7.1 (r271:86832, Jul 31 2011, 19:30:53)
[GCC 4.2.1 (Based on
Just tried the OpenUSB backend under Mac OS X Lion and it does
not seem to work.
import usb.backend.openusb
c=usb.backend.openusb.get_backend()
dlerror: dlopen(/usr/local/Cellar/openusb/HEAD/lib/openusb_backend/darwin.so,
1): Symbol not found: _usbi_devices
Referenced from:
On Sat, Jan 21, 2012 at 10:07 PM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
2012/1/21 Xiaofan Chen xiaof...@gmail.com:
I am not so sure why the libusb-0.1 backend can not enumerate the
device under Mac OS X Lion. Here libusb-compat-0.1 is used
and I built it as universal binary
On Sun, Jan 22, 2012 at 2:59 AM, Peter Bigot
pabi...@users.sourceforge.net wrote:
On Sat, Jan 21, 2012 at 8:09 AM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
I have not commented on this thread because I haven't time to go into
it right now, but I am reading all the posts. Something
On Sat, Jan 21, 2012 at 10:04 PM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
2012/1/21 Xiaofan Chen xiaof...@gmail.com:
Just tried the OpenUSB backend under Mac OS X Lion and it does
not seem to work.
Yes, you're right, OpenUSB backend is not functional yet. I am giving
it low
On Fri, Jan 27, 2012 at 3:04 AM, Paul Shreve robogrou...@gmail.com wrote:
Developers of PyUSB,
I have recently attempted to install your software, PyUSB (version
0.4.3), into my installation of Python 2.6.7, running on Windows XP.
The installation of Python is placed in Python-2.6.7 in my
On Sun, Jan 22, 2012 at 8:39 AM, Xiaofan Chen xiaof...@gmail.com wrote:
Mac OS X implementations of libusb-0.1, libusb-1.0 and
libusb-compat are part of the official libusb distribution.
I have no idea why Mac OSX is failing, I need to look on it
more carefully...
Hopefully there are other
On Fri, Jan 27, 2012 at 9:36 PM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
It seems that this issue has been reported before.
http://comments.gmane.org/gmane.comp.python.pyusb.user/386
So I created a new Trac ticket here.
https://sourceforge.net/apps/trac/pyusb/ticket/10
Thanks,
On Fri, Jan 27, 2012 at 9:58 PM, Xiaofan Chen xiaof...@gmail.com wrote:
It seems that this issue has been reported before.
http://comments.gmane.org/gmane.comp.python.pyusb.user/386
As mentioned in that thread, the problem is with
the enumeration codes.
# implementation of libusb 0.1.x
On Sat, Jan 28, 2012 at 9:59 AM, Xiaofan Chen xiaof...@gmail.com wrote:
The problem is that under Mac OS X, bool(bus)
returns False.
Hmm, that analysis is not correct. The issue is actually
bool(dev) returns false.
Under Ubuntu Linux 11.04, which uses libusb-0.1
legacy, it seems to work
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 order
On Sat, Mar 17, 2012 at 5:15 AM, Emmanuel Blot eblot...@gmail.com wrote:
Hi Wander,
I think latest release of libusb-win32.
What's the backend: libusb 1.x or libusb 0.1? I got controversial
information about it.
libusb-win32 still uses libusb-0.1 API (with extensions on its own
async APIC
On Sun, Mar 18, 2012 at 2:43 AM, Emmanuel Blot eblot...@gmail.com wrote:
I have another question related to the way libusb-win32 manages devices.
I'm using an FTDI 4232H device for the test, along with PyFtdi.
This USB device is a composite one, which contains 4 interfaces, each
of them is
On Wed, Jul 11, 2012 at 5:29 PM, p...@gmx.li wrote:
libusb-1.0 (or the libusbx fork) has Windows support as well
and the dll is named libusb-1.0.dll.
I gave it a try a few days ago.
Like libusbx' README.txt told me, I installed it via a tool named
Zadig.exe, which installed WinUSB
On Thu, Jul 12, 2012 at 2:03 AM, Debapratim Ghosh
deba21pra...@gmail.com wrote:
I am working with python in Ubuntu 11.10. I'm able to detect a USB device,
access its properties etc. Now I want to establish USB communication. As
given in the pyusb tutorial webpage, I gave a command
pingu =
On Thu, Jul 12, 2012 at 6:34 PM, Debapratim Ghosh
deba21pra...@gmail.com wrote:
Hi, the lsusb -v dump of my device shows the following
Bus 005 Device 006: ID 04d8:feaa Microchip Technology, Inc.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB
On Mon, Jul 16, 2012 at 9:34 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Sun, Jul 15, 2012 at 11:36 PM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
2012/7/15 Xiaofan Chen xiaof...@gmail.com:
Same results as before. I am using FreeBSD 9's own
libusb-1.0 and libusb-0.1 wrapper which
On Mon, Jul 16, 2012 at 10:40 PM, Xiaofan Chen xiaof...@gmail.com wrote:
More information.
It seems to me pyusb libusb0 backend is trying to enumerate
the device but somehow does not finish the job properly under
Mac OS X.
mymacmini:test xiaofanc$ export PYUSB_DEBUG_LEVEL=debug
More information.
It seems to me pyusb libusb0 backend is trying to enumerate
the device but somehow does not finish the job properly under
Mac OS X.
mymacmini:test xiaofanc$ export PYUSB_DEBUG_LEVEL=debug
mymacmini:test xiaofanc$ export LIBUSB_DEBUG=4
mymacmini:test xiaofanc$ cat test_libusb0.py
On Tue, Jul 17, 2012 at 10:10 AM, Xiaofan Chen xiaof...@gmail.com wrote:
Now that NetBSD and OpenBSD also have libusb-1.0/libusbx
support along with the legacy libusb-0.1 support. So I would like
to try out pyusb under NetBSD/OpenBSD as well.
Under NetBSD 5.1.2 release, it seems to me
On Tue, Jul 17, 2012 at 6:33 PM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
2012/7/16 Xiaofan Chen xiaof...@gmail.com:
On Tue, Jul 17, 2012 at 10:10 AM, Xiaofan Chen xiaof...@gmail.com wrote:
Now that NetBSD and OpenBSD also have libusb-1.0/libusbx
support along with the legacy
On Tue, Jul 17, 2012 at 6:31 PM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
2012/7/16 Xiaofan Chen xiaof...@gmail.com:
Now that NetBSD and OpenBSD also have libusb-1.0/libusbx
support along with the legacy libusb-0.1 support. So I would like
to try out pyusb under NetBSD/OpenBSD
On Sun, Aug 26, 2012 at 6:54 AM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
PATH_MAX=1024 for OpenBSD 5.1 release and NetBSD 6.0Beta2
using Emmanuel's test program.
Just pushed the fixes for OpenBSD and NetBSD. Thanks, Xiaofan.
Thanks. I can confirm that now libusb0 backend
works
On Thu, Sep 27, 2012 at 9:33 AM, Xiaofan Chen xiaof...@gmail.com wrote:
On Thu, Sep 27, 2012 at 9:17 AM, Bryce Gamble iamhighlan...@hotmail.com
wrote:
I'm running on Windows 7 32-bit.
If I need to install mouse drivers, I may be in trouble.
The real reason I started playing with pyusb
On Thu, Sep 27, 2012 at 9:44 AM, Bryce Gamble iamhighlan...@hotmail.com wrote:
That sounds fantastic! I'm still kind of stumbling a bit with this USB
stuff.
Do you know of any materials I can read to learn more about making our
device generic?
I know there's a USB standard that might supply
On Thu, Nov 8, 2012 at 8:57 PM, Wander Lairson Costa
wander.lair...@gmail.com wrote:
2012/11/8 Stefano Di Martino stefan...@gmx.net:
Is this occurring regardless of OS or it occurs only on Linux/Windows?
If Windows, what backend of libusbx are you using
(winusb,libusbK,libusb-win32) ?
I'm
On Fri, Nov 9, 2012 at 7:06 PM, Stefano Di Martino stefan...@gmx.net wrote:
Well, my solution is nothing else than a deferment, that is,
the problem still exists. It takes longer to show up, but is shows up!
If you can, test your pyusb code inside Linux to see if there
are similar problems or
1 - 100 of 190 matches
Mail list logo
