Re: [pyusb-users] USB Missile Launcher problems with pyusb 1.x

[Racquet B. <bra...@gm...>]

Ah, okay. Maybe the RequestType I'm sending it is wrong? Both uses my exact
model and somewhat describes the usb info in more detail.

https://code.google.com/p/pywws/source/browse/trunk/pywws/WeatherStation.py?r=355

http://matthias.vallentin.net/blog/2007/04/writing-a-linux-kernel-driver-for-an-unknown-usb-device/

It looks like the message for LEFT is:

#define ML_MAX_LEFT     0x04        /* 00 04 00 00 00 00 00 00 */


I change the code to:

dev.ctrl_transfer(0x21, 0x09, 0,0, [ 00,04, 00, 00, 00, 00, 00, 00])

But still got the pipe error.

On Fri, Nov 16, 2012 at 1:17 PM, Tormod Volden <lis...@gm...>wrote:

> On Fri, Nov 16, 2012 at 4:24 PM, Racquet Ball wrote:
> > Thanks for getting back. Here is the output for lsusb:
> >
> >
> > bash-4.2$ lsusb -v -d 1941:8021
> > And here is the stormLauncher.py I had looked over:
> >
> > https://github.com/nmilford/stormLauncher/blob/master/stormLauncher.py
>
> The stormLauncher.py code seems to be written for another device with
> ID 2123:1010. Is there reason to believe your device uses the same
> protocol? An lsusb dump of a device supported by stormLauncher.py
> would help towards answering this.
>
> If you have no information on the device, you might have to resort to
> USB sniffing on the Windows driver (which I assume is available) and
> reverse engineering of the protocol.
>
> Regards,
> Tormod
>
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> pyusb-users mailing list
> pyu...@li...
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>