> Has anyone bought a USB missile launcher and found that my programme
> doesn't control it?
> If you did, and you didn't contact me: why not?  (although my anti-
> spam measures might have prevented some messages from reaching me...)
> Please contact me now.  I've been made aware of another one that
> looks identical to the original, but has entirely different vendor
> ID, product ID and protocol.  Yes, that's right; the protocol is
> entirely different.
> I'm working towards release of this one in the near future, but
> I'd still like to hear from everyone who's got a non-working one
> in case there are yet more different models out there.

> On 14 Oct 2009  Dave Higton <davehig...@dsl.pipex.com> wrote:

> > Has anyone bought a USB missile launcher and found that my programme
> > doesn't control it?
> > If you did, and you didn't contact me: why not?  (although my anti-
> > spam measures might have prevented some messages from reaching me...)
> > Please contact me now.  I've been made aware of another one that
> > looks identical to the original, but has entirely different vendor
> > ID, product ID and protocol.  Yes, that's right; the protocol is
> > entirely different.
> > I'm working towards release of this one in the near future, but
> > I'd still like to hear from everyone who's got a non-working one
> > in case there are yet more different models out there.

> I think there may be more than one problem here. We bought one of
> these for a facetious Christmas present for a Windows-using friend,
> and it's never worked, either on their computer or on my Windows one.
> I bought it via Amazon, and was given a refund without question and
> without having to return it. This makes me think that this was a
> widespread problem with the hardware.

> On 15 Oct, 10:44, Dr Peter Young <pnyo...@ormail.co.uk> wrote:

>> I think there may be more than one problem here. We bought one of
>> these for a facetious Christmas present for a Windows-using friend,
>> and it's never worked, either on their computer or on my Windows one.
>> I bought it via Amazon, and was given a refund without question and
>> without having to return it. This makes me think that this was a
>> widespread problem with the hardware.
> What are its USB Vendor ID and Product ID?  Does it at least work
> enough to give those?

> On 16 Oct 2009  davehigton <davehig...@dsl.pipex.com> wrote:

> > On 15 Oct, 10:44, Dr Peter Young <pnyo...@ormail.co.uk> wrote:
> [snip]

> >> I think there may be more than one problem here. We bought one of
> >> these for a facetious Christmas present for a Windows-using friend,
> >> and it's never worked, either on their computer or on my Windows one.
> >> I bought it via Amazon, and was given a refund without question and
> >> without having to return it. This makes me think that this was a
> >> widespread problem with the hardware.

> > What are its USB Vendor ID and Product ID?  Does it at least work
> > enough to give those?

> Sorry for the delay, it's been more-than usual chaos here. I've
> deleted the software, but the launcher's box says it's Nipco 50820. It
> looks to me as if the rockets are firmly attached to the base!

> In message <1e3137ac50.pnyo...@pnyoung.ormail.co.uk>
>           Dr Peter Young <pnyo...@ormail.co.uk> wrote:
>> On 16 Oct 2009  davehigton <davehig...@dsl.pipex.com> wrote:

>>> On 15 Oct, 10:44, Dr Peter Young <pnyo...@ormail.co.uk> wrote:
>> [snip]

>>>> I think there may be more than one problem here. We bought one of
>>>> these for a facetious Christmas present for a Windows-using friend,
>>>> and it's never worked, either on their computer or on my Windows one.
>>>> I bought it via Amazon, and was given a refund without question and
>>>> without having to return it. This makes me think that this was a
>>>> widespread problem with the hardware.

>>> What are its USB Vendor ID and Product ID?  Does it at least work
>>> enough to give those?

>> Sorry for the delay, it's been more-than usual chaos here. I've
>> deleted the software, but the launcher's box says it's Nipco 50820. It
>> looks to me as if the rockets are firmly attached to the base!
> To find the USB VID and PID from an Iyonix:
> - Plug the device in
> - Open a TaskWindow (Ctrl-F12) and type "usbdevices"
> - Take the number from the first column, on the line relating to the
>   device in question
> - Type "usbdevinfo n", replacing n with the number from the previous step
> - You'll now see several lines, two of which quote the Vendor ID and
>   Product ID.

> On 18 Oct 2009  Dave Higton <davehig...@dsl.pipex.com> wrote:

> > In message <1e3137ac50.pnyo...@pnyoung.ormail.co.uk>
> >           Dr Peter Young <pnyo...@ormail.co.uk> wrote:

> >> On 16 Oct 2009  davehigton <davehig...@dsl.pipex.com> wrote:

> >>> On 15 Oct, 10:44, Dr Peter Young <pnyo...@ormail.co.uk> wrote:
> >> [snip]

> >>>> I think there may be more than one problem here. We bought one of
> >>>> these for a facetious Christmas present for a Windows-using friend,
> >>>> and it's never worked, either on their computer or on my Windows one.
> >>>> I bought it via Amazon, and was given a refund without question and
> >>>> without having to return it. This makes me think that this was a
> >>>> widespread problem with the hardware.

> >>> What are its USB Vendor ID and Product ID?  Does it at least work
> >>> enough to give those?

> >> Sorry for the delay, it's been more-than usual chaos here. I've
> >> deleted the software, but the launcher's box says it's Nipco 50820. It
> >> looks to me as if the rockets are firmly attached to the base!

> > To find the USB VID and PID from an Iyonix:

> > - Plug the device in
> > - Open a TaskWindow (Ctrl-F12) and type "usbdevices"
> > - Take the number from the first column, on the line relating to the
> >   device in question
> > - Type "usbdevinfo n", replacing n with the number from the previous step
> > - You'll now see several lines, two of which quote the Vendor ID and
> >   Product ID.

> OK, done, but don't waste too much time on it, as I'm going to throw
> the wretched thing out anyway. Here is what is says it is:

> USB release     : 0110
> Device class    : 00
> Device subclass : 00
> Device protocol : 00
> Max packet size : 08
> Vendor ID       : 1130
> Product ID      : 0202
> Device ID       : 0100
> Manufacturer    : ''
> Product         : 'Tenx Nonstandard Devic'
> Serial number   : ''
> # of configs    : 1

> In message <86c8a1ac50.pnyo...@pnyoung.ormail.co.uk>
>           Dr Peter Young <pnyo...@ormail.co.uk> wrote:

>> OK, done, but don't waste too much time on it, as I'm going to throw
>> the wretched thing out anyway. Here is what is says it is:

>> USB release     : 0110
>> Device class    : 00
>> Device subclass : 00
>> Device protocol : 00
>> Max packet size : 08
>> Vendor ID       : 1130
>> Product ID      : 0202
>> Device ID       : 0100
>> Manufacturer    : ''
>> Product         : 'Tenx Nonstandard Devic'
>> Serial number   : ''
>> # of configs    : 1
> That's the one I wrote drivers for.
> Have you (a) put known good batteries in it (sorry, but we must
> check the basic things first!)

> and (b) tried it with my driver on a RISC OS computer with a USB interface?

> On 19 Oct 2009  Dave Higton <davehig...@dsl.pipex.com> wrote:

> > In message <86c8a1ac50.pnyo...@pnyoung.ormail.co.uk>
> >           Dr Peter Young <pnyo...@ormail.co.uk> wrote:

> [snip]

> >> OK, done, but don't waste too much time on it, as I'm going to throw
> >> the wretched thing out anyway. Here is what is says it is:

> >> USB release     : 0110
> >> Device class    : 00
> >> Device subclass : 00
> >> Device protocol : 00
> >> Max packet size : 08
> >> Vendor ID       : 1130
> >> Product ID      : 0202
> >> Device ID       : 0100
> >> Manufacturer    : ''
> >> Product         : 'Tenx Nonstandard Devic'
> >> Serial number   : ''
> >> # of configs    : 1
> > That's the one I wrote drivers for.
> > Have you (a) put known good batteries in it (sorry, but we must
> > check the basic things first!)

> Yes, twice, but good thinking, Batman :-)

> > and (b) tried it with my driver on a RISC OS computer with a USB interface?

> Not yet. I'm sorry to be lazy (I have a lot on that which I am pleased
> to call my mind at the moment), but can you remind me where to get the
> driver from? I will try that sometime, but for the time being I'm
> afraid it's low priority.

> On 20 Oct, 11:24, Dr Peter Young <pnyo...@ormail.co.uk> wrote:
>> On 19 Oct 2009  Dave Higton <davehig...@dsl.pipex.com> wrote:

>>> That's the one I wrote drivers for.
>>> Have you (a) put known good batteries in it (sorry, but we must
>>> check the basic things first!)

>> Yes, twice, but good thinking, Batman :-)

>>> and (b) tried it with my driver on a RISC OS computer with a USB interface?

>> Not yet. I'm sorry to be lazy (I have a lot on that which I am pleased
>> to call my mind at the moment), but can you remind me where to get the
>> driver from? I will try that sometime, but for the time being I'm
>> afraid it's low priority.
> http://www.apts04.dsl.pipex.com

> Thanks, got it. However, as mentioned, it may be a while before I do
> any more with it.

> In message <8e4731ad50.pnyo...@pnyoung.ormail.co.uk>
>           Dr Peter Young <pnyo...@ormail.co.uk> wrote:

> > Thanks, got it. However, as mentioned, it may be a while before I do
> > any more with it.

> And if anyone's interested, I'm working on a new USB missile
> launcher application that will control both the old TenX one
> and the newer Satzuma one with the Winbond controller chip.
> It also provides a single application that runs regardless
> of whether the RISC OS machine runs the Castle or Simtec USB
> stack.

> (Except that I'm not sure whether it will work on an
> A9Home.)