Skip to main content

GAGA-1: Integration testing

And so it came to pass that I made the final solder joint to the GAGA-1 flight computer a little before midnight and was able to do an integration test of it and the recovery computer inside the capsule.

Here's the completed Arduino shield that has the GPS (top left), temperature sensors and radio transmitter (bottom middle) that makes up the flight computer. The gold SMA connector at the bottom right connects to the external antenna for telemetry transmission. The three pin connector above the transmitter connects to the external temperature sensor.

And here's a picture of the mounted flight and recovery computers ready for mounting inside the capsule.

And so I duly placed it in the GAGA-1 capsule and powered everything up and... it didn't work. Which was a bummer, but this is why I do these tests.

The following problems were discovered:

1. The DTR switch on the recovery computer is flaky. Sometimes it doesn't stick and hence the computer doesn't start running. In the event this happens on the day it's possible to connect to the computer and issue an AT#EXECSCR command to force start up.

2. The RTTY telemetry was garbled. This was a surprise and seems to be caused by the GPS module's interrupts. Added a new interface to disable and enable interrupts during RTTY send and the RTTY seemed stable.

3. The flight computer GPS was happily getting a lock and the packets containing the lock were being received correctly, but no fix was being recognized. This is because of the way I was handling translation of floating point numbers. The Lassen IQ sends a 4 byte IEEE 754 single precision number byte-by-byte to the Arduino which must then convert this to an Arduino float (which is exactly the same format). The cast I was using wasn't working and it's been replaced by a union:
union float32 {
  BYTE bytes[4];
  float value;

#define COPY_SINGLE(_a,_b)            \
  {                                   \
      union float32 temp;             \
      temp.bytes[0] = packet[_b];     \
      temp.bytes[1] = packet[_b+1];   \
      temp.bytes[2] = packet[_b+2];   \
      temp.bytes[3] = packet[_b+3];   \
      last._a = temp.value;           \
After that the recovery computer worked well and I received many SMS messages with the correct latitude and longitude of the middle of my back garden and an indication of the internal module temperature (around 15C).

The flight computer also worked, but it needs a second test before I'll be totally satisfied. I've yet to see a green bar on DL-FLDIGI indicating a successful decode of the GAGA-1 telemetry. This is essential for the tracker.

In other news the weather is still looking good for launch on Sunday. Here's the most recent prediction for 0900 UTC on April 10, 2011:

And GAGA-1 is getting a last minute addition. James Coxon asked if he could piggy back a Hellschreiber beacon on GAGA-1. So GAGA-1 will be flying with RTTY on 434.650 Mhz (the dial frequency I had last night was 434.652 Mhz) and Hellschreiber on 434.075 Mhz.


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 last name …

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.0image 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), r, h, floor(m…

Importing an existing SSL key/certificate pair into a Java keystore

I'm writing this blog post in case anyone else has to Google that. In Java 6 keytool has been improved so that it now becomes possible to import an existing key and certificate (say one you generated outside of the Java world) into a keystore.

You need: Java 6 and openssl.

1. Suppose you have a certificate and key in PEM format. The key is named host.key and the certificate host.crt.

2. The first step is to convert them into a single PKCS12 file using the command: openssl pkcs12 -export -in host.crt -inkey host.key > host.p12. You will be asked for various passwords (the password to access the key (if set) and then the password for the PKCS12 file being created).

3. Then import the PKCS12 file into a keystore using the command: keytool -importkeystore -srckeystore host.p12 -destkeystore host.jks -srcstoretype pkcs12. You now have a keystore named host.jks containing the certificate/key you need.

For the sake of completeness here's the output of a full session I performe…