Feeds

LOHAN cranks up old-school clockwork failsafe

Rocket motor ignition back-up gets the tick-tock treatment

  • alert
  • submit to reddit

High performance access to file storage

We're obliged to Low Orbit Helium Assisted Navigator (LOHAN) fans for answering our call for suggestions as to just how a back-up ignition system for our Vulture 2 spaceplane's rocket motor might work.

Click here for a bigger version of the LOHAN graphicOur primary system is the Special Project Electronic Altitude Release System (SPEARS) control board, but we want a purely mechanical standby, just in case SPEARS goes titsup.

A "last-resort" option is something which works at or after balloon burst, such as our idea of using the opening of the payload parachute. It's a high-risk strategy, since there's not much air at altitude, and god alone knows just how the payload will behave as it tumbles through the stratosphere until the parachute deploys.

It does, though, have the advantage of being splendidly simple, as our original cunning plan graphic demonstrates:

Graphic of our proposed mechanical failsafe mechanism

In reality, we probably wouldn't even need the complex tube/spring/plunger assembly; an strip of insulation between two spring-loaded contacts would probably do the job.

With this in mind, we though we'd unfurl LOHAN's payload parachute - actually a rocket recovery model - and give the basic idea a spin. Here's the parachute laid out flat...

The LOHAN rocket recovery parachute laid out

...and here's our test rig:

The parachute, cardboard payload box, rigging and igniter lines

What we've got is the "failsafe line" attached to one parachute strap just under the canopy, passing though a ring tied to the opposite strap, then the swivel between the payload tathers and the 'chute straps, and ultimately tied to a simple steel wire pin stuck into the top of a cardboard box payload.

Here's the failsafe line at the parachute end. Note that in the best traditional of garden-shed boffinry, we used a wooden curtain ring that happened to by lying around:

The igniter line attached to the parachute canopy, and passing through a wooden ring on the opposite side

The failsafe line then passes through the top of the swivel. It doesn't necessarily need to pass through the swivel at all, but we thought this was the best way of avoiding it gradually winding round either the payload tethers or parachute straps during the ascent:

The igniter line passing through the swivel

We'll have more on the matter of twisting in due course. In the meantime, enjoy our hi-tech test pin mechanism:

The igniter line attached to a length of steel wire poked into the top of the box

We calculated the slack in the line to be sufficient to avoid premature tugging, but not enough that the pin wouldn't get a sharp pull when the parachute opens.

So, with a bit of extra weight in the box to simulate the mass of our fantastical flying truss, we chucked the thing off a high building to see how it works.

Well, it does work, but there certainly is an issue with the line getting wound up as the swivel, er, swivels, as many of you predicted. The solution may be a bearing, like this one:

An aluminium bearing suitable for use a LOHAN swivel

We reckon we can attach the flying truss to the outside of the bearing, and the parachute lines to the inside, with the failsafe line passing through the hole in the middle. You get the idea.

However, that will have to wait, since our immediate priority is a pre-balloon-burst back-up for the SPEARS board, due to fly for the second time on 13 July.

The test flight is intended to ensure SPEARS will fire Rob Eastwood's custom igniter, which has two inputs connected to separate E-Matches:

Rob Eastwood's diagram of his custom LOHAN igniter

So, SPEARS is using one connection, and the other will be hooked up to a decidedly old-school piece of tech, viz: a clockwork oven timer:

A 120-minute clockwork timer

Yes indeed, in the best tradition of garden shed boffinry, we took this entirely mechanical device, rigged it to a 9V battery holder and "pull to change" safety switch...

The timer rigged to a battery holder and safety switch

...stuck the whole thing in a plastic box...

The timer and switch installed inside a plastic box

...and added some fetching graphics:

The front of the box, with the timer dial and switch

The safety switch is required because the timer switch is a double pole, double throw unit, and the output side is live until the timer is set. Accordingly, to avoid premature ignition, it's necessary to set the timer running and then "arm" the unit.

Regarding accuracy, it's pretty good. Here are the results:

  • Timer set at 20 minutes: 20min 10s - 19min 52s - 20min 53s - 20min 46s - 20min 0s
  • 40 minutes: 40min 25s - 39min 57s - 41min 14s - 40min 42s - 40min 06s
  • 80 minutes: 81min 14s - 81min 15s - 81min 40s - 81min 50s - 81min 07s
  • 120 minutes: 121min 26s - 121min 15s - 121min 25s - 121min 23s - 121min 22s

Since we can predict the balloon rate of ascent pretty accurately, we'll be able to set the timer to fire the igniter just after SPEARS should have done it anyway. And voilà - we have our first failsafe system ready to roll.

The timer can, of course, be connected to the same battery pack SPEARS will use to fire the igniter, so we won't need extra batteries. Our one concern is that it might freeze up at altitude, so we're mulling some preventative measures to address that.

We can be certain of one thing, though, it works at ground level. Works like a charm, in fact:

Watch Video

®


Further LOHAN resources:

  • New to LOHAN? Try this mission summary for enlightenment.
  • You can find full LOHAN coverage right here.
  • Join the expert LOHAN debate down at Reg forums.
  • All the LOHAN and Paper Aircraft Released Into Space (PARIS) vids live on YouTube.
  • For our SPB photo archive, proceed directly to Flickr.
  • We sometimes indulge in light consensual tweeting, as you can see here.

LOHAN - A Special Projects Bureau production in association with...

  • 3T RPD logo
  • University of Southampton logo
  • Applied Vacuum Engineering logo
  • Escher Technologies
  • Flashpoint Fireworks logo
  • HAB Supplies logo
  • Rock 7 logo

Paper Aircraft Released Into Space

High performance access to file storage

More from The Register

next story
Elon Musk's LEAKY THRUSTER gas stalls Space Station supply run
Helium seeps from Falcon 9 first stage, delays new legs for NASA robonaut
Solar-powered aircraft unveiled for round-the-world flight
It's going to be a slow and sleepy flight for the pilots
Russian deputy PM: 'We are coming to the Moon FOREVER'
Plans to annex Earth's satellite with permanent base by 2030
LOHAN's Punch and Judy show relaunches Thursday
Weather looking good for second pop at test flights
Saturn spotted spawning new FEMTO-MOON
Icy 'Peggy' looks to be leaving the outer rings
Discovery time for 200m WONDER MATERIALS shaved from 4 MILLENNIA... to 4 years
Alloy, Alloy: Boffins in speed-classification breakthrough
India's GPS alternative launches second satellite
Closed satnav system due to have all seven birds aloft by 2016
Curiosity finds not-very-Australian-shaped rock on Mars
File under 'messianic pastries' and move on, people
Top Secret US payload launched into space successfully
Clandestine NRO spacecraft sets off on its unknown mission
prev story

Whitepapers

Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
HP ArcSight ESM solution helps Finansbank
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Mobile application security study
Download this report to see the alarming realities regarding the sheer number of applications vulnerable to attack, as well as the most common and easily addressable vulnerability errors.