 -GCM-320+ recording Geiger counter -Mobius Mini Action Camera -AP510 APRS tracker -TK106 GSM backup tracker -Outside Hung Compact Rain-Activated Pull-down -Directed Arborial Recovery Node with Integrated Tether -and the Pi Zero with camera, GPS, and LoRa modules This was then connected to a 81cm chute and a 1000g cell will 2300g of neck lift from H2. Tim W. and Jim C. and their families joined in to help with launch, chase, and recovery. Chris G. acted as remote Public Affairs Officer. The flight projection for Sunday promised a lazy zigzag with a landing very near the launch point. Paul decided to launch from Lake Benson Park in Garner. That would put the landing area in a part of the county that had the least amount of forests. Problems with the payload began at activation of the equipment. Paul hadn't performed integration tests with the various gear prior to flight and although the camera and Pi themselves were RF shielded from the tracking gear, there was a rather apparent interference issue. Once put together in the same box, none of the three trackers could maintain a GPS lock. The problem wasn't fully realized until the balloon had been inflated. So Tim was stuck having to hold the big balloon while Paul took time to troubleshoot. The team guessed that the local oscillator from the Pi GPS was causing interference for the other GPS receivers. Eventually Paul decided to simply cut the power line to the Pi GPS unit and continue with the countdown. This left the Pi without GPS info, but it would still continue to take photos and relay them via LoRa. After that, it was a matter of launching and keeping our fingers crossed. The balloon rose nearly straight up and the crew was able to watch it for a very long time. LoRa data came down steadily and error free until the payload drifted horizontally out of range at an altitude of 11km. Sadly, we were also having issues with the LoRa gateway and only a handful of the packets received actually got sent on to the Habhub website. Due to the Pi no longer having a GPS, the system simply re-transmitted its launch coordinates. It also never scaled up its photo size as it was programmed to do at higher altitudes. So all Pi images were limited to 640x480.   Pi image as taken and transmitted at 9.1km vs what was received and posted to Habhub.  Thumbnails of the Pi images that were transmitted via LoRa Sample Pi image (click to see at 640x480)  Stills during ascent from the Mobius Mini videoDuring much of the ascent, the team stayed at the launch site and played with the LoRa receiving gear. Eventually they headed for the air conditioning of the chase cars and made way to the projected landing area.   Mobius stills over 100,000 feet  The parachute never stood a chance Hanging from a tree 6 feet above the ground Flight visualization  A rather normal ascent followed by a descent at 3x the normal speed. The payload stayed quite warm due to solar heating.   #8 closest landing to the launch siteNotes from Paul: This is what flight tests are all about. I have some RF tests to do to see what can be done about the GPS problem. What part needs the extra shielding? It may be easier to simply put the PiInTheSky in a small capsule hanging a few meters below the standard payload. The transmission mode should be changed from "Turbo" down to "SSDV" mode (Although I had problems making that work in the lab). The TK106 had issues and only really worked once it was removed from the payload after landing. Is there an issue between the AP510 and the TK106 as well? I will need to chat with Dave Akerman to see what I can do to improve the performance of the LoRa Gateway. We had decent Internet out in the field. There were others using SSDV that day so maybe there was contention on the server end. |
Missions >
