Re: Tricky USB device.

2005-04-09 Thread David Gilbert
Bernd == Bernd Walter [EMAIL PROTECTED] writes: Bernd Yes - you must use 1 - there is only one out-endpoint. 0x81 is Bernd for receiving data and endpoint 0 is the mandandory control Bernd endpoint. Interrupt Endpoints are not variable in size. Both Bernd interrupt endpoints are 8 Bytes, so

Re: Tricky USB device.

2005-04-09 Thread David Gilbert
Bernd == Bernd Walter [EMAIL PROTECTED] writes: Bernd Then the device is still working and just has nothing to send. Bernd Would be helpfull to know something about the protocol used on Bernd the endpoints. It's pretty simple. I'm sending (right now) MK255 and MK0 with 1 second sleeps in

Re: Tricky USB device.

2005-04-09 Thread Bernd Walter
On Sat, Apr 09, 2005 at 05:48:43PM -0400, David Gilbert wrote: Bernd == Bernd Walter [EMAIL PROTECTED] writes: Bernd Then the device is still working and just has nothing to send. Bernd Would be helpfull to know something about the protocol used on Bernd the endpoints. It's pretty

Re: Tricky USB device.

2005-04-09 Thread David Gilbert
Bernd == Bernd Walter [EMAIL PROTECTED] writes: Bernd Sounds simple. Tried with lower case characters? Otherwise I Bernd would say sniff a working driver - for windows there is at Bernd least one good freeware USB sniffer avaiable. HA! Found the problem --- thank-you everyone. Aparently,

Tricky USB device.

2005-04-08 Thread David Gilbert
I've got an OnTrak ADU208. It's a USB device that has 8 relays and 8 ttl inputs. The documentation says it uses two interupt endpoints ... one input and one output. It seems to expect small text commands. Now... firstly, uhid is probing it as uhid0: uhid0: www.ontrak.net ADU208 USB Relay I/O

Re: Tricky USB device.

2005-04-08 Thread Maksim Yevmenkin
David, I've got an OnTrak ADU208. It's a USB device that has 8 relays and 8 ttl inputs. The documentation says it uses two interupt endpoints ... one input and one output. It seems to expect small text commands. ok Now... firstly, uhid is probing it as uhid0: uhid0: www.ontrak.net ADU208 USB

Re: Tricky USB device.

2005-04-08 Thread David Gilbert
Maksim == Maksim Yevmenkin [EMAIL PROTECTED] writes: ... I don't know if this is hindering me. The usbhid* commands aren't particularly helpful. The port udesc_dump seems only to work on ugen devices ... and ugen doesn't pop up for this device. Maksim how about getting usb hid descriptor,

Re: Tricky USB device.

2005-04-08 Thread Maksim Yevmenkin
David, ... I don't know if this is hindering me. The usbhid* commands aren't particularly helpful. The port udesc_dump seems only to work on ugen devices ... and ugen doesn't pop up for this device. Maksim how about getting usb hid descriptor, parsing and dumping it? Maksim check out libusbhid

Re: Tricky USB device.

2005-04-08 Thread David Gilbert
Maksim == Maksim Yevmenkin [EMAIL PROTECTED] writes: Maksim David, ... I don't know if this is hindering me. The usbhid* commands aren't particularly helpful. The port udesc_dump seems only to work on ugen devices ... and ugen doesn't pop up for this device. Maksim how about getting usb

Re: Tricky USB device.

2005-04-08 Thread Bernd Walter
On Fri, Apr 08, 2005 at 12:56:16PM -0400, David Gilbert wrote: Maksim == Maksim Yevmenkin [EMAIL PROTECTED] writes: ... I don't know if this is hindering me. The usbhid* commands aren't particularly helpful. The port udesc_dump seems only to work on ugen devices ... and ugen doesn't

Re: Tricky USB device.

2005-04-08 Thread David Gilbert
Bernd == Bernd Walter [EMAIL PROTECTED] writes: Bernd Then it really shouldn't have claimed to be one in the Bernd interface descriptor :( But the HID specification is more today Bernd than just _human_ interface. e.g. there are extensions for Bernd USV, ... [...] Bernd Has this device

Re: Tricky USB device.

2005-04-08 Thread Maksim Yevmenkin
David, Bernd Then it really shouldn't have claimed to be one in the Bernd interface descriptor :( But the HID specification is more today Bernd than just _human_ interface. e.g. there are extensions for Bernd USV, ... [...] Bernd Has this device multiple interfaces? e.g. one HID and another

Re: Tricky USB device.

2005-04-08 Thread Bernd Walter
On Fri, Apr 08, 2005 at 03:32:56PM -0700, Maksim Yevmenkin wrote: hmm... why even use libusb? cant you just fd = open(/dev/ugen0.1, O_RDWR); and then write(fd, MK255, 5) and read(fd, ...);. note: here i assume ugen0 is the device. I'm also not entirely clear how/when to use

Re: Tricky USB device.

2005-04-08 Thread Bernd Walter
On Fri, Apr 08, 2005 at 06:12:33PM -0400, David Gilbert wrote: Bernd Has this device multiple interfaces? e.g. one HID and another Bernd as described. I often thought about getting ugen working at Bernd interface level too. Here's the output of udesc_dump on it. Right now, using the

Re: Tricky USB device.

2005-04-08 Thread Maksim Yevmenkin
Bernd Walter wrote: On Fri, Apr 08, 2005 at 06:12:33PM -0400, David Gilbert wrote: Bernd Has this device multiple interfaces? e.g. one HID and another Bernd as described. I often thought about getting ugen working at Bernd interface level too. Here's the output of udesc_dump on it. Right now,

Re: Tricky USB device.

2005-04-08 Thread Bernd Walter
On Fri, Apr 08, 2005 at 04:47:43PM -0700, Maksim Yevmenkin wrote: Bernd Walter wrote: On Fri, Apr 08, 2005 at 06:12:33PM -0400, David Gilbert wrote: Bernd Has this device multiple interfaces? e.g. one HID and another Bernd as described. I often thought about getting ugen working at Bernd

Re: Tricky USB device.

2005-04-08 Thread Julian Elischer
Maksim Yevmenkin wrote: Bernd Walter wrote: On Fri, Apr 08, 2005 at 06:12:33PM -0400, David Gilbert wrote: Bernd Has this device multiple interfaces? e.g. one HID and another Bernd as described. I often thought about getting ugen working at Bernd interface level too. Here's the output of

Re: Tricky USB device.

2005-04-08 Thread Bernd Walter
On Fri, Apr 08, 2005 at 06:06:30PM -0700, Julian Elischer wrote: Maksim Yevmenkin wrote: Bernd Walter wrote: On Fri, Apr 08, 2005 at 06:12:33PM -0400, David Gilbert wrote: Yes - you must use 1 - there is only one out-endpoint. 0x81 is for receiving data and endpoint 0 is the mandandory