Skip to main content

GAGA-1: The Stack

I'm calling the combination of balloon, parachute and capsule "the stack". Here's a diagram of how GAGA-1 will fly:

The balloon is attached to 2mm climbing cord which has a strength of 120 daN (decanewtons). That corresponds to roughly 120x the force of gravity on a 1kg mass. As the capsule has a mass of roughly 1kg there's plenty of safety margin (unless things get really hairy in the jet stream).

4m of cord attach the top of the parachute (where is has an X for that purpose) to the balloon. The balloon is 4m above the parachute so that when the balloon bursts the remnants fall well clear of the parachute and don't get tangled. Note that the parachute is open at all times, when ascending it's pulled taut by the lift from the balloon; once the balloon is gone the parachute simply opens slowing the descent.

To keep the remnants hanging down on 4m of cord away from the capsule there are 8m of cord between the bottom of the parachute and the capsule attachment. You can see the cord bundles in the photograph above. They are attached to the parachute using double bowline with a stopper.

On the capsule there are cords that pass through the polystyrene itself (I pierced it with a long metal skewer and threaded the cord through). Here's a shot of the capsule hanging by its four cords. On the top are the two GPS antennas, the GSM backup antenna for the recovery computer, and the small black tube is the external temperature sensor sticking through.

On the bottom you can make out the UHF antenna that will transmit telemetry to the ground (there's a cardboard cover protecting it which will be removed before flight).

Here's the underside showing the cord threaded through.

And here's the top where the cords come through both the capsule and its cover.

Comments

Popular posts from this blog

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands . They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0 image by Shinji I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring): The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30). The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {     float m = (360-30*float(h))*2/13;     int s = round(60*(m-floor(m)));     int col = h%6;     int row = floor(h/6);     draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1),

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of