Skip to main content

GAGA-2: Mounting the flight computer

On GAGA-1 the flight computer was screwed in place using nylon bolts that went through the polystyrene walls of the capsule. GAGA-2 is using cable ties.

One concern with cable ties is their performance at low temperature. The CUSF guys had warned me never to use cable ties for load bearing joints. But since we are holding in place a few grams of flight computer the only remaining concern was whether the cable ties would still be locked at low temperature.

So, I locked together a pair of ties and left them in the freezer at -18C overnight.

The next morning they showed no signs of slippage and I was unable to pull them apart. But for double safety I've also superglued the locking part of the cable ties shut in place.

Here's the flight computer inside the capsule:

There are a pair of cable ties around the two board of the flight computer (the Arduino and the custom shield on top containing the radio transmitter and the GPS). Those help keep them together.

Then there are a pair of cable ties that pass through the wall of the inner capsule. Those cable ties are hot glued in place so there are no holes and so they don't move.

Finally the two sets of cable ties are interleaved so that the board is held in place. Once everything is tightened I dropped superglue in all the locking parts. The computer is positioned so that there's no stress on the rather short cable to the GPS antenna.

It doesn't move and I'm pretty happy that it'll stay in place during the flight. The next thing that needs mounting securely is the battery. On GAGA-1 the batteries popped out on landing; I'm not letting that happen this time.


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