Skip to main content

GAGA-1: Computer mounting

Not much time to work on GAGA-1 this weekend, so I nailed down one of the simpler items: how the two computers (flight and recovery) are going to be mounted inside the capsule. After considering all sorts of techniques I settled on self-adhesive Velcro "coins" and a cut up fast food container (the plastic containers that much Indian food comes in have nice fitting lids and are made of strong plastic: I use them for storing screws, components and all the miscellaneous stuff in my basement).

Here's a picture of an untouched curry container and once I cut up. The two black dots are Velcro pads on I stuck on the bottom. The container is just the right width to fit in the box and the small vertical portion pushes against the edges of the box keeping it snug. Between that and the Velcro this will provide adequate support for the two computers.


With the two computers sitting on it, it's clear that there's adequate space. The computers will be attached using screws and risers that I have left over from an ancient robot project.


Finally, here's a shot inside the capsule itself showing the Velcro pads that are stuck directly to the polystyrene.


The other thing I spent time on was deciding on interfacing for the Telit GSM862 module. I toyed with the idea of buying a SparkFun USB Evaluation Board to make the module easy to program, but the price put me off. It's very expensive just to get a USB interface.

Since the module will be flown attached to a simple breakout board (see the photo above), I decided that I'll interface directly to that board for programming using a USB TTL converter cable. That way I can program the device in place... cheaply. The breakout board will only have three additional things attached to it: power, an LED on the STAT_LED pin, and a simple switch on the ON/OFF pin.

Note that in the circuit diagram for the SparkFun GSM862 Basic Evaluation Board (the breakout board I'm using), it's not obvious that all four of the VCC connections on the Telit module are connected together, and both the GND connections are connected together. This is super convenient because it means only one of each needs to be connected to the battery, but the SparkFun circuit diagram is incorrect in showing six separate connections. A quick test with a multimeter and a look at the PCB tracks verifies the truth.

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