Skip to main content

GAGA-1: Getting close to completion

The last time I updated on GAGA-1 it was when I cut the hole for the camera. Since then I've had a little time to work on it and things are getting close to completion. There's still a bunch of software to write for the flight computer, but that shouldn't take long. The launch will now be in the early spring when the winds are favourable.

First, here's a nice shot of where I was. It shows the interior of the capsule with the recovery computer mounted in place, a rough location for its battery pack and the camera. The two SMA connectors are for the GPS and the GSM antennas.

The first thing I did was make a couple of battery connectors with leads of the right length. I've bought two battery holders (one holds 4 AAs for the recovery computer, the other holds 6 AAs for the flight computer). Both have snap on connectors in the PP3 style and so I soldered up some short leads.

The next job was to shorten the leads on the GSM and GPS antennas. They came with leads 5m long and I needed to get them down to a few cms otherwise there would be excess weight from useless wire. I cut the leads and soldered on new SMA connectors.

This was a total pain to do (any excess solder on the pin in the connector and inserting it was a nightmare). Finally, I got the three done with much poor language. Looks like there's some braid that needs trimming in this photograph:

Next job was fitting in notice to the outside of the box in case it gets lost. This is a piece of paper that's been laminated and then hot glued to the outside (I've masked my phone number here but it is on the real box). Inside the box there's the same message printed on a small piece of paper just in case the outer one was lost somehow.

To reduce the impact of Murphy's Law I painted all the connectors with colours that match so that I don't do something stupid like connect the GPS to the GSM antenna or wire up the wrong battery.

Then it was on to the flight computer radio. This consists of a Radiometrix NTX2 connected to the Arduino flight computer using a custom board. Here's the partially constructed board. It mounts on top of the Arduino and subsequently I've added a couple of resistors and an SMA socket.

The radio, of course, needs an antenna and for this purpose I built my own 1/4 wave, ground plane antenna tuned to the frequency at which GAGA-1 will transmit. It consists of five pieces of cut up coat hanger. Each piece if 16.4cm long (1/4 of the wavelength of the GAGA-1 transmitter).

Four of the pieces are joined together and form the ground plane; there are mounted flat against the bottom of the capsule. The fifth piece points downwards and is mounted at right angles to the ground plane. The ground plane is connected to the braid of a small piece of coax recovered from the GSM antenna wire I cut; the central piece is connected to the coax central conductor. The coax has a new SMA connector on the end for connection to the flight computer.

Finally, I painted and hot glued polystyrene balls to the ends of the antenna pieces to stop me (or others) getting poked by it. Here's a shot of GAGA-1 on its side with the antenna in place (the pieces are held together by a small round piece of plastic I found in my box of random stuff).

Some final tasks to perform are:

1. Fit the Lassen IQ GPS to the Arduino board
2. Write the flight computer software
3. Connect up the DS1821+ temperature sensors

Then I'll be ready for a full system test.

PS Having got all this stuff done I did a quick weigh in by shoving everything in the box (batteries and as yet unsoldered components). It weighed in at 989g. Pretty close to my original desire for 1kg.

PPS I will publish a schematic of the Arduino board when it's done.

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