Now that the iPhone SDK has been released it’s time to start thinking about how the iPhone or iPod Touch could be used to control and fire missiles from the USB Missile Launchers. So I’ve been thinking…

1. Missile Luncher(s) are connected to a Mac running USB Missile Launcher NZ software

2. iPhone/iPod Touch software uses accelerometer to control axis movement of the launcher and touching the screen fires the launcher

How will it work internally?

We’ll I don’t know nearly enough about the SDK yet. The USB Missile Launcher NZ software is AppleScript enabled. So the thought is that if the iPhone application can send through AppleScript events to the Mac running the USB Missile Launcher NZ software then we have a winner!

The hard bit here is that I don’t have an iPhone or iPod touch with which to test and I live outside the US and cannot enrol the iPhone developer program at this point. If anyone wants to try developing this idea I look forward to hearing from you.

- David

Looks like they have been up since mid December and anyone is free to register. Here’s the link http://dreamlink.info/dream/forum

It is available for download from the downloads section on the left.

Enjoy.

Details of changes in this release.

• Correct issues with Installer Maker packaging not working (something to do with spaces in file names?)
• Have received actual Rockey Baby Launcher for testing, testing completed – up/down/right/left/fire all working – also detected correctly full travel movement responses from launcher
• Correct application launch issues when kext not installed and causes application crash
• Found and fixed a bug in the FindInterfaces USB code, this may have effected some launcher operations
• Adding support for new DreamCheeky Launcher (internal name = RocketBaby)
• Added new kext for RocketBaby support
• Added code to DeviceAdded to read the HID Descriptor (the RocketBaby won’t work properly unless this is done). It is now done for all launchers
• Enhanced application version checking code
• Added message to display window if launcher is actually connected at application start
• Added “Prime Fire” button – works for two models of DreamCheeky launcher. This means that there is now a shorter time to actually fire when you do fire.

Please refer to the download links on the left of this page to get your updated release.

Note: I have had some issues with the PackageMaker under Leopard while trying to get this release produced. As a consequence, the folder that is installed within the Applications folder on your machine has been renamed to have the spaces removed file from name. You may be left with the old folder in the Application directory, this can be removed.

For anyone trying to do their own coding for this launcher, here are the updated control codes:

// Set up Packet - 21 09 00 02 00 00 00 00
//
// 0x01 - down
// 0x02 - up
// 0x04 - left
// 0x08 - right
// 0x10 - fire
// 0x20 - stop
// 0x40 - request status
//
// 1. To fire, Send 0x10
// 2. The motor keeps working now, keep sending 0x40 to ask for status (say, every 100~500ms)
// 3. If 0x00 received, then the missile is not fired.
// 4. If 0x10 received, them missile is fired.
// 5. If the missile is fired, send 0x20 to stop it.
//
// Other launcher Responses - these are returned as bits and thus you need to check like "if (rbBuffer[0] & 0x01)" using Bitwise AND
// 0x01 - all the way down
// 0x02 - all the way up
// 0x04 - all the way left
// 0x08 - all the way right
// 0x10 - fire has completed

Wireless USB Missile Launcher

USB Missile Launcher with Web CAM 

I don’t have these launchers and at this point do not offer support in the Mac version of the Missile Launcher software for them. But boy would I love to get my hands on these!

Thanks to a group of dedicated testers and in particular one with a USB Protocol Analyser we do have a release of the USB Missile Launcher NZ software that you can use with your Mac. I have not been able to test this release against the RocketBaby launcher as I don’t have one … yet … One of these launchers is in transit to me though it now seems unlikely that it will arrive on my doorstep before Christmas.

The testing team have reported good things at this point with the software, it now controls the launcher and fires… though there may be some things that don’t work so well (like the diagonal commands).

Downloads:

These are at different locations to the normal ones as I am not happy to replace the normal download links at this stage, I don’t what the other supported launchers to break especially while I’m away over the next week or so. Though I’d be surprised if there were any issues. All downloads here a relative to the v1.4.9 build 140 release.

Installer within Disk Image package – this is for everyone

Source code package – if you want to play.

You will need Xcode installed, and probably Xcode 3 as supplied with Leopard. There is more work to do on this release and I hope to do that once I get my hands on the launcher. If anyone has suggestions or even changes the code themselves to make improvements I’d really like to see what you’ve done and get the source updates so that the software can evolve.

Unfortunately I do not have one of these launchers and making slight code changes at the USB driver level and sending them offshore for overnight or 1, 2, 3 days turn around is proving to be very frustrating. 

I really need someone to send me one of the launchers! 

The launcher does move, uncontrollably at this stage, the issues are occurring when I’m trying to get feedback from the launcher on its status.

Attempts in this space are causing the software to lock up. I did find a very good USB web site last night and have been doing more reading on the “readPipe”, and I’m now awaiting feedback from off shore. 

Being able to get hold of one of these launchers would significantly speed up development for the enjoyment of all.

What would also possibly help is if anyone else, maybe in the Linux community, has some code that will drive one of the DreamCheeky “RocketBaby” Rocket Launchers. 

usbVendorID: 2689(0xa81) usbProductID: 1793(0×701)

Device Name: Rocket Baby 

// USBVendorID  = 2689 (0xa81)

// USBProductID = 1793 (0×701)

// Controls 

// 01  – down

// 02  – up

// 04  – left

// 08  – right

// 10  – fire

// 20  – stop

// 40  – request status

//

// 1. To fire, Send 0×10

// 2. The motor keeps working now, keep sending 0×40 to ask for status (say, every 100~500ms)

// 3. If 0×00 received, then the missile is not fired.

// 4. If 0×10 received, them missile is fired.

// 5. If the missile is fired, send 0×20 to stop it. 

OK, so that’s all good news. The question you want answered is when will the launcher work with the Mac Missile Launcher software? Well, I’ve been trying… It’s difficult to get it working when I don’t actually have one of these launchers (even when I have the details of the launcher control codes). I’m working with some internet citizens at the moment who have offered to help with the testing. No luck yet, I’ll post again when a new version is available. 

• Altered default preference settings. Resolves issue of laser not working properly on Striker II and stops duplicate commands being sent to Striker II and Original launcher. Existing users can install updated application and manually “zero” settings for launcher types that are defined twice (vendor ID = 4400, and product ID = 514) or reset defaults.
• Distribution now includes a script providing integration with “Sofa Control 2.0″ – you can use your Apple Remote to control the launcher! – http://caseapps.com/sofacontrol.html (thanks to rawketcato for providing this). To use the script you will need to go to the Installed Scripts menu in Sofa Control and import the script that is included with this distribution.
• Fixed a problem controlling the Original launcher (Striker I).

If you have had problems with the USB Missile Launcher NZ software and the Striker II laser not working correctly, I think I have a solution.

The issue lies with the default preference settings and how they are interpreted by the program. The easy fix for this is to remove or change the preference settings so that the software does not think duplicate launchers exist. Follow the instructions below:

1. Run the launcher software
2. Go to preferences
3. select the launcher icon
4. Change Launcher 3 (or Launcher 1) setting of Vendor ID and Product ID both to 0 (zero). err, so that I make that clearer, I’ll explain again…
5. –> launcher 1 should have vendor ID of 4400 and Product ID of 514 with laucher type of Striker II
6. –> launcher 3 should have vendor ID of 0 and Product ID of 0 and we don’t care about the launcher type.
7. Click the apply button
8. Quit the program
9. rerun the program and test laser

This evening I have also fixed an issue regarding control of the original launcher. After some testing, release 1.4.8 should be out soon.

Included with the 1.4.8 distribution will be a script that can be imported into “Sofa Control” – this means that you can use your apple remote to control the launcher!

Camera support is included, though it did not work for me running under Parallels on my MacBook Pro, your millage may vary. One really nice feature is the ability to prime the missile firing tank, this significantly reducing the delay between pressing the fire button and the actual fire. The “slow motion” feature is another nice touch. Once activated the diagional movement buttons are removed.

I can confirm for Mac uses that the software does run under Parallels on Windows XP.

Make sure that you download and install the 1.2 version of the SharpLauncher software. Anthony has made the source code for this release available as well – it’s a real bonus!

Anthony Mason’s web site for the Sharp Launcher.

Download links for the installer, documentation, and source code are available on Anthon’s web page.

Major work has gone into diagnosing an issue regarding control of the DreamCheeky launchers where it appears as though a new version of the hardware was being very strict on the control sequences that were sent to it. I’d like to thank everyone who has helped with the diagnosis of this issue, your help is very much appreciated.

Included in this release is:

• Added German Language translation
• Altered some diagnostic code to help isolate problems with Striker II and DreamCheeky support
• Fixed an error where incorrect USB parameters were being sent to the DreamCheeky launcher
• Fixed an error where the “end of travel” for the DreamCheeky launcher was not being detected properly
• Fixed an error where some Striker II laser was not working
• Added “debug” option to General preferences. Output is sent to the Console.log file – warning this can be _very_ verbose
• Added Applescript support, refer to the application AppleScript dictionary for command set and example in readme document
• Added application startup check for required kext files – warning message issued if they are missing
• Dramatically improved the Fire sequence for DreamCheeky launchers, now reads feedback from launcher when fire completes, two or more DreamCheeky launchers connected at the same time will fire sequentially.

One of the exciting new developments is the addition of AppleScript support. You can now issue launcher control commands via applescript as shown below:
tell application “USB Missile Launcher NZ”
unlock
move right seconds 2
move left seconds 2
move up seconds 1
move down seconds 1
fire
delay 7
lock
end tell

As always for more information please have a look at the readme file that is included with the release.

I have updated the source code distribution for this release, it is available as a separate download from the link on the downloads section of this web site.

devRequest.bmRequestType = USBmakebmRequestType(kUSBOut, kUSBClass, kUSBInterface);
devRequest.bRequest = 0x09;
devRequest.wValue = 0x0000200;
devRequest.wIndex = 0;
devRequest.wLength = 8;
devRequest.pData = reqBuffer;

The special key here is wValue of 0×200 (though I have no idea what it does).

The next development update is for AppleScript support! This works:

tell application "USB Missile Launcher NZ"
unlock
move right seconds 2
move left seconds 2
move up seconds 1
move down seconds 1
fire
delay 7
lock
end tell

And… I _may_ have fixed the issue with the laser not working correctly on the Striker II.
I have also added a check on application startup to verify that the require kext files are installed in /System/Library/Extensions. The application lets you continue to run, though does provide a warning that things may not function as expected.

AppleScript support has been a bit of a mission. It’s working! Not sure I’ve implemented it in an ideal way though.
Here’s an example script:
tell application "USB Missile Launcher NZ"
unlock
moveleft
delay 1
abort
moveright
delay 1
abort
movedown
delay 1
abort
moveup
delay 1
abort
fire
delay 3
abort
lock
end tell


You get the idea.

Known Problems
Two issues have been reported to me this month

1. On the Striker II the laser only “blinks once” when you try to activate it. I have not been able to resolve this.

2. Two other users, both with MacBook Pro’s have reported that their DreamCheeky launchers do not work with the USB Missile Launcher NZ software, though it does on the same machine under parallels. So far through may e-mails and exchange of files, I have been able to identify (c/- System Profiler) that under Software/Extensions the IOUSBFamily file does not have a “Integrity:Correct” setting (like mine). And on at least one of the machines the IOUSBCompositeDriver, IOUSBHIDDriver, and IOUSBUserClient client is now shown. I’m still seeking more information on this, initial thoughts are that the OS install is corrupted and that a re-install of the OS may be required (Archive and Re-Install).

What’s new in this release?

• Added joystick detection
• Added preference pane for joystick support, ability to control sensitivity and reversal of X and Y axies
• Added preference pane for launcher support. This allows users to change the USB Product ID and USB Vendor ID and Launcher type. Provides support for 3 Launcher products/vendors.
• Fixed potential memory leak in my USB code
• Application icon is changed to a DreamCheeky Rocket if it is the first or only launcher connected
• Added support for the Striker II Launcher – the Laser checkbox will only work on the Striker II

Note 1: This release will reset existing user preferences on first application launch.
Note 2: Tested joysticks include: Logitech Attack 3, Saitek Cyborg Evo Wireless.
Note 3: The introduction of the launcher preference pane is a potential foundation for allowing users to enter launcher control codes thus eliminating the requirement for a software release when new launchers are made available.

Known Issues
Striker II
WARNING – You cannot have the the Original Missile Launcher and the Striker II connected to the Missile Launcher NZ software at the same time.

For Those wishing to use the Striker II, you need to go to the preferences (launcher panel) and change the drop down menu from OrigLauncher to StrikerII, click the Apply button. Then quit and restart the application.

Some problems were experienced during the testing process that have not yet been completely resolved. To setup your Striker II access the Launcher preference pane. Make sure that the Vendor ID = 4400 and the Product ID = 514 and set the Launcher Type to StrikerII. You then must click the Apply button and quit and restart the launcher program. The unresolved issue is that the Striker II may have to be in the Launcher 1 slot in the preferences or that the Origional Launcher is left undefined.

Program output can be found in the console.log (run the console program in the utilities folder to see the messages emitted by the program).

Joysticks
A new feature in version 1.4f I have been able to test the software with only a limited number of joysticks. So far my testing has met with a 75% success. The joystick that did not work as rather old. I have not been able to undertake more testing with this particular device. Your milage may vary.

Please click in the download link in the sidebar.

Good luck with your office warfare!
Happy hunting!

Testing of the new software release has gone global, no really it has! And I need to thank those who have contributed to the development and testing cycle. It’s been extremely hard to test without a launcher sitting next to me. What we found is that the manufacturers documentation didn’t work and the implementation needed some educated guess work.

I’m holding off on a release at the moment as one of the last reports still had issues with the Laser on the Striker II and an application crash as well, unfortunately I have no further details to go on. If there are any Striker II users closer to New Zealand, I wouldn’t mind hearing from you if you’d like to do a bit of testing for me.

The joystick integration has gone well. Everything works on 3 of the joysticks that I have tested. A 4th much older joystick didn’t work at all, it was purchased abck in the Mac OS 9 days.

- David

I need to obtain the documentation that is supplied with the Striker II Missile Launcher. The documentation is supposed to include details of the USB codes that are used to control the launcher.

This web site makes reference to it.

If you have one of these, can you e-mail me the documentation if you have my e-mail address, or leave a comment to this posting and I will mail you back. Thanks.

I have two joysticks here, a Logitech Attack 3 and a Saitek Cyborg Evo Wireless. As it turns out not all USB joysticks are created as equals and I am having some difficultity with the Saitek. So I have more work to do before I can build a release for distribution.

And thanks to some feedback today I’ve built another preference pane, this time called Launcher. The idea is that the user can define the USB Vendor ID and USB Product ID to add additional launcher support. Of course this may or may not work.

I will carry on attempting to understand USB devices and working with them. What I probably need is a “Programming USB for Dummies Guide”. It could be quite a popular title if it actually existed.

What’s in the updated 1.4e release?

• Added preference option for Camera enable/disable on startup
• Message change for Launcher not connected when application starts
• Added Preference option to reverse arrow keys
• Updated kext drivers for DreamCheeky and the USB Missile Launcher
• Added code that reads back the USB codes from the DreamCheeky Launcher so that it now does not exceed launcher travel limits
• Source code will be available separately (it is been removed from the release file to reduce the size of the distributed file)

Please click in the download link in the sidebar.

Also in the side bar is a download link to the source code package.

See the BLOG home page for the latest Missile Launcher Developments http://dgwilson.wordpress.com.

I have a DreamCheeky Rocket Launcher as you know. I also have a PowerMac G4 (specifically the AGP graphics version otherwise known as the Sawtooth model). This machine comes with 2 x 12MBit/s USB ports. I have never had any success getting the DreamCheeky Launcher working on this machine. The DreamCheeky Launcher says on the box that it requires a USB 1.1 port.

So this morning I went to the local electronic shop (Dick Smiths) and purchased a PCI USB 2.0 card.

When I got home, I shutdown the G4, opened the case, installed the card, and started up the G4.

All good so far.

Connected the DreamCheeky Launcher to the USB 2.0 port on the card.

Ran my USB Missile Launcher NZ software and it’s working wonderfully. For added good measure I connected the original USB Rocket Launcher to the keyboard and that worked too.

Huge success tonight. I at last have been able to read data back from the DreamCheeky Rocket Launcher. This means that I can detect when the launcher has reached a point beyond which it should not travel (i.e. full up, full left, full right, full down).

There is some work to do now to actually use the information that I have above, though that should be relatively straight forward now.

I have also impletemented two preference options as requested by YOU!

• Disable the camera – so that it doesn’t come on when the program starts
• Reverse of arrow keys (well the left and right anyway).

Bad News:

I will be away for a week or so shortly. No e-mail, no Internet!

I do not have any time now to complete the DreamCheeky USB changes. This will unfortunately have to wait.

Better News:

My faulty machine, as reported below, was diagnosed as requiring a new motherboard, but was fortunately covered by the Apple Repair Extension program for the eMac. It was estimated to be 2 weeks before the parts were available and this should be about the same time I get back from holiday.

All the best.

Aim Carefully!

I don’t have my eMac back from the repair shop yet, I’ve been told that could take another two weeks. A very kind friend has loaned me his second machine so this evening I have managed to complete the packaging job for the Mac OS 10.3.9 release fo the USB Missile Launcher NZ software. [I have received confirmation that this release also works on Mac OS 10.2.8] This is version 1.3.3. There is no additional functionality included in the release other than the support for the DreamCheeky Rocket Launcher. Good luck, happy targeting.

I have removed the source code from this distribution, essentialy so that I can have the v1.3.3 release online and available for download, this makes it significantly smaller. If you are interested in the source code, I’m happy to mail you the source code package, though for the moment you will still need to e-mail me.

Plecase click on the download link in the sidebar for the latest release.

I need to package the release (in the next day or two) and make it available for download. I will update this post when it is ready.

[31 December 2006] Update: There is a holdup with the release of the software. Sorry. My development machine has been crashing and I’ve spent some considerable time investigating the reason as to why. Looks like the video card in my eMac (basically the motherboard) is toasted!

It’s all rather nasty. The log below isn’t mine (it is all but identical to mine though).

Nov 23 11:53:32 gilva kernel[0]: ** ASIC Hang Log Start **
Nov 23 11:53:32 gilva kernel[0]: 0x01005c63 4f000217 00000007 00000003
Nov 23 11:53:32 gilva kernel[0]: 0x0200a859 c0001c04 00000002 00000008
Nov 23 11:53:32 gilva kernel[0]: 0×00004443 01e1f827 00000e0e 80010140
Nov 23 11:53:32 gilva kernel[0]: 0x4000ffff 001e0000 51b3a220 72001005
Nov 23 11:53:32 gilva kernel[0]: 0x080a0f00 00000000 040100f8 80000003
Nov 23 11:53:32 gilva kernel[0]: 0x0008bbbb 00000002
Nov 23 11:53:32 gilva kernel[0]: 0:0x000101ce
Nov 23 11:53:32 gilva kernel[0]: 1:0×10014020
Nov 23 11:53:32 gilva kernel[0]: 2:0×00000002
Nov 23 11:53:32 gilva kernel[0]: 3:0x000101ce [about 1020 lines more of similar kernel messages]Nov 23 11:53:42 gilva kernel[0]: 1021:0xffffffff
Nov 23 11:53:42 gilva kernel[0]: 1022:0xffffffff
Nov 23 11:53:42 gilva kernel[0]: 1023:0xffffffff
Nov 23 11:53:42 gilva kernel[0]: 0x56500bb3
Nov 23 11:53:42 gilva kernel[0]: ** ASIC Hang Log End **
Nov 23 11:53:42 gilva kernel[0]: ATIRadeon::submit_buffer: Overflowed block waiting for FIFO space. Have 5, need 6. RBBM_STATUS 0×80010140. VAP_CNTL_STATUS 0×00000002
Nov 23 11:53:53 gilva kernel[0]: ** ASIC Hang Log Start **
Nov 23 11:53:53 gilva kernel[0]: 0x01005c63 4f000217 00000007 00000003
Nov 23 11:53:53 gilva kernel[0]: 0x0200a859 c0001c04 00000002 00000008
Nov 23 11:53:53 gilva kernel[0]: 0×00004443 01e1f827 00000e0e 80010140
Nov 23 11:53:53 gilva kernel[0]: 0x4000ffff 001e0000 51b3a220 72001005
Nov 23 11:53:53 gilva kernel[0]: 0x080a0f00 00000000 040100f8 80000003
Nov 23 11:53:53 gilva kernel[0]: 0x0008bbbb 00000002
Nov 23 11:53:53 gilva kernel[0]: 0:0x000101ce
Nov 23 11:53:53 gilva kernel[0]: 1:0×10014020
Nov 23 11:53:53 gilva kernel[0]: 2:0×00000002
Nov 23 11:53:53 gilva kernel[0]: 3:0x000101ce
Nov 23 11:53:53 gilva kernel[0]: 4:0×10016020

The updated 1.4d has added support for DreamCheeky Rocket Launcher:

• updated driver (kext) for USB Missile launcher to Universal Binary
• created driver (kext) to support DreamCheeky Rocket launcher (Universal Binary)
• launcher software controls both launchers at the same time
• updated driver (kext) source code included in distribution
• changed internal code for smoother control of the launcher (eliminating stop/start motion that is not present when you use the keyboard controls)
• when controlling the launcher you can use the numeric keypad. For the DreamCheeky Rockey Launcher at least, you will get a finer motion control over the launcher
• this release has had some problems in testing (I get an occasional “beach ball” – it pauses the application for a bit and goes away). As of this release the issue has not been identified

Warning:

This release has had some problems in testing (I get an occasional “beachball” – it pauses the application for a bit and goes away). As of this release the issue has not been identified

Tips:

When controlling the launcher you can use the numeric keypad. For the DreamCheeky Rockey Launcher at least, you will get a finer motion control over the launcher.

ReadMe

Please see the included ReadMe.rtf file for more details.

Plecase click on the download link in the sidebar for the latest release.