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

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

Many thanks, friend. Your command with the wValue set to 0x200 worked. The
machine wasn't broken after all!

On Mon, Nov 19, 2012 at 5:21 PM, Tormod Volden <lis...@gm...>wrote:

> On Mon, Nov 19, 2012 at 4:20 PM, Racquet Ball wrote:
> > Sorry for the late rely. I tried:
> >
> > dev.ctrl_transfer(0x21, 0x09, 0,0, '0x04')
> >
> > But the pipe error is still there. Could it be just the device is broken
> (I
> > don't have the windows driver for this)?
>
> The kernel driver sends a data buffer of 8 bytes (command + 7 null
> bytes) so it would be like this:
> dev.ctrl_transfer(0x21, 0x09, 0, 0, [command, 00, 00, 00, 00, 00, 00, 00])
>
> The SnoopPro snapshot shows a wValue of 0x200 in the requests,
> although the kernel driver uses 0. I suppose the kernel driver was
> tested, but you can still try out:
> dev.ctrl_transfer(0x21, 0x09, 0x200, 0, [command, 00, 00, 00, 00, 00, 00,
> 00])
>
> If other code that is proven to work on other people's devices (of
> same USB ID) does not work on your device, it could be the device is
> broken, yes... Did you already try WeatherStation.py and Vallentin's
> kernel driver?
>
> 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
>