Re: [pyusb-users] interruptWrite gives unknown USB error

On Thu, Jun 3, 2010 at 9:14 AM, Xiaofan Chen 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 struggle with FreeBSD

Re: [pyusb-users] interruptWrite gives unknown USB error

On Wed, Jun 2, 2010 at 11:56 PM, Ct Chev wrote: > and I get the following error: > Traceback (most recent call last): > File "usbenum.py", line 46, in > handle.interruptWrite(2, "*IDN?\n") > usb.USBError: Unknown error > > Output from usbenum.py: > > Device: /dev/ugen2.3 So are you using FreeBS

Re: [pyusb-users] interruptWrite gives unknown USB error

Hi, 2 things. 1. Read the USB TMC specification, it has a structure that must wrap the commands to the device. See test measurement class on this page 2. The Agilent USB DAQ devices I have used in the past use a cypress EZ-usb chip

[pyusb-users] interruptWrite gives unknown USB error

Hello,   I am trying to send SCPI (text) commands to an Agilent U2100A Digital IO via USB.  I have used Python to send SCPI commands to other equipment successfully in the past using the parallel port or over ethernet.  However this is my first time working with a USB device and Python. I can s

Re: [pyusb-users] XP

I have XP Professional Ver 2002 SP2. Libusb0.sys is in windows\system32 \drivers & libusb0.dll is in windows\system32 and Python25\Lib \site-packages. Thanks, I'll try the libusb-win32 mailing list for some help. Mark > Sorry I am running out of ideas. Could you try the latest > 1.1.14.0 release

Re: [pyusb-users] XP

On Wed, Jun 2, 2010 at 9:15 PM, Mark wrote: > My testlibusb-win.exe output (with my device connected & showing up ok > in device manager) gives only the DLL ver, program ver & other header > information - no device output. Clicking refresh does nothing. > > Running enumusb.py with or without my de

Re: [pyusb-users] XP

On Wed, Jun 2, 2010 at 9:15 PM, Mark wrote: > My testlibusb-win.exe output (with my device connected & showing up ok > in device manager) gives only the DLL ver, program ver & other header > information - no device output. Clicking refresh does nothing. > > Running enumusb.py with or without my de

[pyusb-users] XP

My testlibusb-win.exe output (with my device connected & showing up ok in device manager) gives only the DLL ver, program ver & other header information - no device output. Clicking refresh does nothing. Running enumusb.py with or without my device connected gives only this output: found 4 busses