On Wed, March 16, 2011 08:04, Xiaofan Chen wrote:
> On Wed, Mar 16, 2011 at 1:06 AM, wander.lairson
> wrote:
>
>>> Should I use pyUSB for this application? What are the pitfalls of
>>> simply writing to /dev/hidraw0?
>>>
>> If the driver provides what you need, you do better using it.
>>
>
> Yes
On Wed, Mar 16, 2011 at 1:06 AM, wander.lairson
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 permission
>> to /dev/hidr
2011/3/15 Andrew Errington :
> On Sun, 13 Mar 2011 23:34:49 wander.lairson wrote:
>>
>> You have only one out endpoint, endpoint 1. It is probably this
>> endpoint you should write to, but before it you must select this
>> interface through a call to set_interface(1,1).
>
> I'm sorry, I don't reall
On Sun, 13 Mar 2011 23:34:49 wander.lairson wrote:
>
> You have only one out endpoint, endpoint 1. It is probably this
> endpoint you should write to, but before it you must select this
> interface through a call to set_interface(1,1).
I'm sorry, I don't really understand how it all works. I stil
2011/3/13 Andrew Errington :
> On Fri, 11 Mar 2011 19:37:36 wander.lairson wrote:
>
> I'm not sure. SnoopUSB tells me there is no endpoint involved (it is n/a),
> and you can see in the XML I sent it is -1, so I don't know. I am sure it is
> supposed to be endpoint 0x83 on interface 3.
>
> Here i
On Fri, 11 Mar 2011 19:37:36 wander.lairson wrote:
> 2011/3/10 Andrew Errington :
>
> [snip]
>
> > How do I do this in pyUSB? So far I have managed to identify the device,
> > detach the driver (for interface 3, the HID interface) and I can read the
> > state of the GPIO pins (but I cannot write t
2011/3/10 Andrew Errington :
[snip]
>
> How do I do this in pyUSB? So far I have managed to identify the device,
> detach the driver (for interface 3, the HID interface) and I can read the
> state of the GPIO pins (but I cannot write to them).
>
> Hints and tips would be welcome.
>
What endpoint
2010/12/22 Venkat, Karthikeyan :
> Hello everyone,
>
> I am a total newbie to pythonUSB.
>
> I am using the PyUSB interface for one of the devices which has a FTDI chip.
>
> I could read the device ID and get the serial number of it.
>
> I need to read and write data to the device.
>
> The example
Hello everyone,
I am a total newbie to pythonUSB.
I am using the PyUSB interface for one of the devices which has a FTDI chip.
I could read the device ID and get the serial number of it.
I need to read and write data to the device.
The example provided on the website is not sufficient to read
On Wed, December 22, 2010 05:50, Tormod Volden wrote:
> On Tue, Dec 21, 2010 at 1:36 PM, Andrew Errington wrote:
>
>> code and a compiled binary. Unfortunately the binary was compiled for
>> a different Product ID than the device I have. Doubleplus unfortunately
>> the source code for the .lib fi
On Wed, December 22, 2010 01:55, wander.lairson wrote:
>
> Visual C++ free edition does not ship MFC, and as I guess you don't
> want to buy Visual C++ Pro just to compile the sample application, I
> recommend you using Platform SDK or DDK (yes, DDK may be used to compile
> applications) to rebuild
On Tue, Dec 21, 2010 at 1:36 PM, Andrew Errington wrote:
> code and a compiled binary. Unfortunately the binary was compiled for a
> different Product ID than the device I have. Doubleplus unfortunately the
> source code for the .lib file which actually sends the data packets to the
> device is a
2010/12/21 Andrew Errington :
> Hello,
>
> I contacted the manufacturer of the sound card device I am working with. They
> sent a data sheet, so I have the I/O pin numbers. They also sent me some
> software to read and write bytes to the GPIO registers. This was some source
> code and a compiled
13 matches
Mail list logo
