Comment Re:What would be interesting... (Score 1) 174
It is not as simple as it seems, let me give a few examples:
For these sorts of experiments, you absolutely must be able to find the payload after landing - and though you may be able to simulate roughly where it will land, you really have no idea. You have to have a really high confidence that your communication system is going to allow you to find the payload wherever it lands. In Australia, even the best two options (GSM and APRS) have rather patchy coverage. GSM is great near populated areas, but these are obviously not the best areas for launch and landing. Outside populated areas there is weak, or often no GSM reception at all. Likewise, most of the APRS infrastructure is located around areas where people live and are going to use it. Then of course there is the physical recovery, what happens if the balloon lands in the wilderness hundreds of kilometres from roads? What if it lands in the sea? Before you can really do anything fancy you really need to verify that you launch/recovery system works absolutely perfectly.
OK, so now you've got your GPS receiver and transmitters. How is your GPS location data affected by the transmitter going off next to it? How about serial comms? Could the NMEA data be corrupted when the transmitter goes off? I2C sensors? How will it affect communication with the SD-CARD? How will you know? How will the transmitter affect the rest of your system? How will the system be affected by low temperatures? What happens if one module fails, what will the system do to recover? It's good stuff for an engineering project, but perhaps not an extremely interesting story in itself.
You have many interesting ideas which really would make a project unique, in my case though it was enough of a handful already just getting the basics done myself while coping with the rest of Uni study/life. I'll try something more unique for my next launch.