Skip to main content

GAGA-1: flight computer testing

Having got the flight computer radio working with my homebrew antenna it was time for a couple of tests: test that the radio could actually transmit over a reasonably long distance and see how long the flight computer would keep running for.

Here's GAGA-1 ready for its trip (I made a little cover for the antenna to protect it on the journey):

The capsule will get lifted to over 30km and I'm using a 10mW radio transmitter. As others have shown this works fine with line-of-sight and a good antenna. To run the test I got a helping hand from my parents who dropped me off at one end of Abberton reservoir with my Yaesu FT-790R and a Yagi antenna while they drove off to Abberton church with GAGA-1 sitting on the backseat transmitting a short RTTY message. The total distance between the two points was almost exactly 5.5km.

Got a few funny looks from birdwatchers and families as I stood there (although one person was kind enough to take my picture, see below).

As they drove away I left the radio receiver on the ground with a little whip antenna on it. This was able to pick them up almost the entire way (at some points the signal fading, and while at the church there was a lot of noise).



Switching to the Yagi made the signal come in loud and clear, so loud and clear in fact that they never bothered to get out of the car. Over 5.5km from inside a car parked inside a copse the transmitter was working fine at the other end of this shot:

Here's an action shot of me with the Yagi pointing vaguely in GAGA-1's direction. The signal was so strong with the Yagi that pointing it in pretty much any direction worked.

The final test for the day was to let the flight computer run and see how it fared. After 8 hours of continuous transmission I pulled the plug on the test. The final transmission was $$GAGA,24.8,Error: 0 which indicated that the internal capsule temperature was 24.8C and that the external sensor was not connected.

Here's a picture of the flight computer left and recovery computer on the right before mounting inside the box.

And here's a view inside the capsule showing the mounted computers with batteries. Doing this I discovered that I'd mounted the battery packs in positions that made inserting the camera really hard and no clearance for the antenna SMA connector. Had to remove and reglue.

Comments

Popular posts from this blog

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

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

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