If the device is a USB -> parallel converter, it should behave like a
parallel port, so why don't try to use it as a parallel port?
2011/7/8 Emilio Bellini :
> Hi all,
> I'm sorry if this is a stupid question.
> I want to control a circuit, which has 8 relè, and I want to switch them
> on/off via
Hi all,
I'm sorry if this is a stupid question.
I want to control a circuit, which has 8 relè, and I want to switch them
on/off via software. Originally my idea was to control it using a parallel
port, but my laptop hasn't it. So, I'm trying to use an USB port with an USB
to Parallel converter. I c
2011/1/11 Xiaofan Chen :
> On Mon, Jan 10, 2011 at 9:24 PM, wander.lairson
> wrote:
>> 2011/1/10 Xiaofan Chen :
>>> On Mon, Jan 10, 2011 at 8:41 PM, Xiaofan Chen wrote:
>>>
It seems my Cygwin Ctypes does not have WinDLL.
I am not so sure if this is the problem. Last time I
rebuilt
On Mon, Jan 10, 2011 at 9:24 PM, wander.lairson
wrote:
> 2011/1/10 Xiaofan Chen :
>> On Mon, Jan 10, 2011 at 8:41 PM, Xiaofan Chen wrote:
>>
>>> It seems my Cygwin Ctypes does not have WinDLL.
>>> I am not so sure if this is the problem. Last time I
>>> rebuilt libusb-1.0 using cdecl, now it only
On Wed, Jan 5, 2011 at 11:40 PM, Xiaofan Chen wrote:
> On Wed, Jan 5, 2011 at 10:45 PM, Emmanuel Blot 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 e
On Mon, Jan 10, 2011 at 9:19 PM, Xiaofan Chen wrote:
> On Mon, Jan 10, 2011 at 8:41 PM, Xiaofan Chen wrote:
>
>> It seems my Cygwin Ctypes does not have WinDLL.
>> I am not so sure if this is the problem. Last time I
>> rebuilt libusb-1.0 using cdecl, now it only supports
>> stdcall under Windows
On Mon, Jan 10, 2011 at 9:24 PM, wander.lairson
wrote:
> 2011/1/10 Xiaofan Chen :
>> On Mon, Jan 10, 2011 at 8:41 PM, Xiaofan Chen wrote:
>>
>>> It seems my Cygwin Ctypes does not have WinDLL.
>>> I am not so sure if this is the problem. Last time I
>>> rebuilt libusb-1.0 using cdecl, now it only
2011/1/10 Xiaofan Chen :
> On Mon, Jan 10, 2011 at 8:41 PM, Xiaofan Chen wrote:
>
>> It seems my Cygwin Ctypes does not have WinDLL.
>> I am not so sure if this is the problem. Last time I
>> rebuilt libusb-1.0 using cdecl, now it only supports
>> stdcall under Windows.
>>
>
> It is indeed true un
On Mon, Jan 10, 2011 at 8:41 PM, Xiaofan Chen wrote:
> It seems my Cygwin Ctypes does not have WinDLL.
> I am not so sure if this is the problem. Last time I
> rebuilt libusb-1.0 using cdecl, now it only supports
> stdcall under Windows.
>
It is indeed true under Cygwin.
mc...@mcuee-pc-win7 ~
$
On Wed, Jan 5, 2011 at 9:30 PM, Xiaofan Chen wrote:
> Plain Python 2.6 Windows works fine.
>
Here is a run log under Windows 7 32bit. The firmware used
is Jan Axelson's Generic HID example. The firmware
loops back the HID input and output report.
D:\work\pyusb\pyusb>d:\Python26\python.exe
Python
On Sat, Jan 8, 2011 at 10:04 PM, wander.lairson
wrote:
> Revision 89 fixed libusb-win32 under cygwin. I still have problems
> with libusb-1.0 official cygwin build, it feels like there is no
> symbol exported:
>
> $ objdump.exe -T /usr/bin/cygusb-1.0.dll
>
> /usr/bin/cygusb-1.0.dll: file form
2011/1/5 Xiaofan Chen :
> On Wed, Jan 5, 2011 at 5:21 PM, wander.lairson
> 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
On Wed, Jan 5, 2011 at 10:45 PM, Emmanuel Blot 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 the following er
> Plain Python 2.6 Windows works fine.
I've installed the driver with Zadig for the USB device, which is connected.
Before copying the DLL, I got the "No backend available" error, so I
guess that now the DLL is found.
I've copied
\libusb_2010.12.10\MS64\dll\libusb-1.0.dll into System32, and
On Wed, Jan 5, 2011 at 5:21 PM, wander.lairson 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
libusb-1.0 (build it from sour
> So, maybe it is just a matter of adding /usr/bin for library search
> path. Going to check that when have some time...
AFAICT from my yesterday unsuccessful attempts, ctypes (cygwin /
Python 2.6.5) automatically find the cygusb-1.0.*dll libraries from
/usr/bin, the dedicated "cygwin" case in pyu
2011/1/5 Emmanuel Blot :
>> 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.
>
> The dynamic libraries (cygusb*.dll) are located in /usr/bin/, not in /usr/lib/
> http://cygwin.com/packages/
> 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.
The dynamic libraries (cygusb*.dll) are located in /usr/bin/, not in /usr/lib/
http://cygwin.com/packages/libusb1.0/libusb1.0-1.0.7+gitbd62
2011/1/4 Emmanuel Blot :
>> libusb 1.0 uses WinUSB, which I am not sure is
>> available in Windows XP (I guess so, you might find some info in the
>> libusb.org website)
>
> It seems it is supported since WinXP SP2:
> http://msdn.microsoft.com/en-us/library/ff540196.aspx
> but some specific files
On Wed, Jan 5, 2011 at 3:19 AM, Emmanuel Blot 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 least, if the
> libusb 1.0 uses WinUSB, which I am not sure is
> available in Windows XP (I guess so, you might find some info in the
> libusb.org website)
It seems it is supported since WinXP SP2:
http://msdn.microsoft.com/en-us/library/ff540196.aspx
but some specific files need to be installed.
I missed thi
2011/1/4 Emmanuel Blot :
> Hello,
>
> Did anyone succeed running pyusb (or even libusb...) under Windows ?
>
> I've tried on Windows XP 32-bit the following combinations, without any
> success:
>
> 1. Python 2.6.5/Cygwin 1.7, libusb-win32
> 2. Python 2.6.5/Cygwin 1.7, libusb-1.0.5+git
> 3. Pyth
Hello,
Did anyone succeed running pyusb (or even libusb...) under Windows ?
I've tried on Windows XP 32-bit the following combinations, without any success:
1. Python 2.6.5/Cygwin 1.7, libusb-win32
2. Python 2.6.5/Cygwin 1.7, libusb-1.0.5+git
3. Python 2.6.5/Cygwin 1.7, libusb-1.0.7+git
4. P
Does PyUSB raise any exception? If so, what's the message? If not, has
all the data written?
Wander
2008/3/19, Mike Holloway <[EMAIL PROTECTED]>:
> Hi all,
>
> I'm very new to this list, so hello all!
> I'm just starting out using python, my background is lamp.
>
> I have a Prolific Technologies
Hi all,
I'm very new to this list, so hello all!
I'm just starting out using python, my background is lamp.
I have a Prolific Technologies bridged usb cable that I wish to talk to
using pyusb and libusb, I've tried following examples and compiling my
own code but I'm really struggling getting it
25 matches
Mail list logo