Following in the footsteps of Apex I and its unfortunate loss, Version 2 of the high altitude weather balloon launched by Sutton Grammar School sets out to achieve the same objectives. With a completely redesigned payload and tracking system, we hope to make this version easier to track & find.
This project is complete - the payload has been launched once and more launches are planned. See ApexHAB on Twitter for more information.
We have a PDF detailing the technical hardware on the payload. This can be found here.
Contact us: send an email to our mailing list at firstname.lastname@example.org
The payload on this project is completely different to that of Apex I. The radio system will have a downlink on 434.075 MHz to make use of the distributed listener, following the comms protocol detailed here.
The balloon side radio equipment will consist of one NiM2 narrowband FM transciever from Radiometrix link.
Current designs designate three modes of data transmission. One on the minute, one at 20 seconds past, and one at 40 seconds past. Each transmission will be preceeded by a specific tone denoting the mode. The receiver can adjust itself to the correct decoding system and then decode the packet. This prevents the two becoming de-sync'd: a risk with time based operation.
Radiometrix appnotes seem to suggest that bit balancing is very important with these modules and tone based operation gets around this issue to an extent. The other option is using a proper bipolar encoder.
During Launch 1 we suffered difficulties in decoding due to the combined effect of severe temperature drift and the AFC in dl-fldigi losing track due to the extended radio-off period for uplink. For Launch 2, we will be addressing these issues by using a new transmission regime. We will transmit a packet on 300 baud three times over without radio breaks, just a ~3second carrier gap. Then will come a 50 baud packet with only GPS data (no sensor data), after which will be a ~20second uplink window.
After recommendation from CUSF and with regards to its low cost and lack of altitude limit, the Lassen iQ GPS unit from Trimble looks like a good choice. Runs on 3.3V too, and the current draw is perfectly acceptable for a GPS unit (30-40mA).
The flight computer is likely to be a PIC uP. A PICAXE 40×2 (more GPIOs than 28×2) is very simple but looks like it will be up to the job (can run 4 programs pseudo-simultaneously). Hardware UART for the radio transceiver. GPS will be a bit tricky but should be OK using qualifiers and scratchpad buffer.
Low voltage version (3.3V) available at up to 64 MHz. We will run at default clock rate (8 MHz).
GSM network coverage is scarce when more than 2,000ft above ground level. We'll turn the GSM transmitter on as soon as the balloon starts to descend and as soon as it manages to connect to a GSM network, we'll get it to transmit GPS coordinates, time and altitude. It'll do that ever 5-10 minutes afterwards as well.
We have done away with the Sony Ericsson USB-serial phones as the MAX3421 is very irritating and we can't get it to work, and not through lack of trying. So we'll be using an old phone with a real UART to send SMS messages. Part of the team are working on finding a suitable phone and to get it sending texts from a PICAXE. Their code will be merged into the flight computer one when it's working.
We will be using two Canon Ixus 40 (SD300) CHDK'able cameras, one pointing down and the other across. These will have revised and improved versions of the CHDK control script we flew on Apex I. For a start, the cameras will automatically be set to manual infinite focus so as to not waste time trying to focus on every picture event.
Due to the camera used it is not possible to supply the camera with power externally, making it impossible to power cycle externally. However, it may still be possible to include a power cycle within internal scripting.
For Launch 2, these are being rescripted using LUA to attempt to get around some of the reliability issues we saw during Launch 1 - see the git repo on github for source code.
Our power supply will be 4xAA Energizer Lithium batteries. They retain their capacity even at low temperatures and over a wide range of discharge rates
In either case, regulators will be implemented (Maxim LDOs?) as different systems will require different voltages.
Centronics have been kind enough to provide us with two compact, low weight (7 grams) Geiger-Muller detectors. Gamma & other high energy penetrating radiation will be the kinds these can detect. They need a 400-600V supply but the current should be very, very low (I proportional to radiation level).
A simple 555/transformer based inverter should suffice. A large cap will be needed to try and smooth out recharging and for the inevitable higher discharge rate at altitude. Need some serious decoupling and noise suppression to prevent cap recharging interfering with RF comms.
Possiblity of continuous ADC on the cap terminals to keep charge rate as low as possible whilst maintaining required voltage. The flight computer must disable charging whilst the radio is transmitting to avoid RF/EMI spikes.
A daughterboard to the flight computer PCB will convert the output from these sensors to a count value which the flight computer can request once a minute, before it is reset to 0.
We'll be using the standard AM-SSB capable radio and dl-fldigi to decode the incoming signals from the balloon. It's after that that things get a little more complex.
We would like to be able to visually plot the balloon's position on a map without relying on an internet connection. As such we aim to write software to take data from fldigi and output it to the tracking system we used on Apex I as this worked brilliantly. The data will be fed to APRSPoint and then MapPoint 2004 so we can see the balloon's position on the Mappoint map.
We will have a 3G internet dongle in at least one of the vehicles so decoded data from the radios can be fed to the DL server. Provided we have internet connectivity we can also use the DL tracking web page to see balloon position, altitude, ascent rates, etc. However we aim to implement all this functionality locally so as to not rely on net connection.
The software is called “Apex Packet Handler” and is written in VB.