View source for HSIS/1st Flight

You do not have permission to edit this page, for the following reason:

You can view and copy the source of this page:

BoldItalic

External link (remember http:// prefix)Internal linkEmbedded fileReferenceSignature and timestamp

AdvancedSpecial charactersHelp

Level 2Level 3Level 4Level 5

Heading

FormatBulleted listNumbered listIndentationNo wiki formattingNew line

BigSmallSuperscriptSubscript

InsertPicture galleryTableRedirect

== 1st Test Flight of Payload - 4/10 & 4/11 Flight Windows == === Flight Readiness === ==== Must Be Ready ==== Here's what needs to be ready for flight: * Payload ** Photography *** Cold Test In Freezer - '''Passed''' with an endurance of 2.5 hours for an uninsulated camera with flash and screen turned off manually and scripted to take a picture every 10 seconds. Camera battery was at 25% at the end of the test and the memory card was not full. *** Photo Test - See Above, '''Passed'''. ** Thermal Control *** Cold Test - From Bill Brown; using the solar-heated clear bubble wrap method has been flown and proven. Therefore, it '''will be accepted and used this flight'''. * Recovery ** Water Landing Readiness - In the event we land in water. Currently using a foam block and ziplock bag packed in with the bubble-wrapped payload. '''Will need to test this.''' * Lifting Hardware ** Balloon - '''Ready for the 4/11 Window'''. Two, 800-g weather balloons in our posession. Will not be required for the 4/10 launch. ==== Optional ==== For the 4/10 launch, tracking, lifting and recovery hardware will be provided by UAH and Bill Brown. For the 4/11 launch, tracking and recovery hardware and lifting gas will be provided by Bill Brown. Therefore, our preparations for them on each respective window are optional. * Tracking ** Primary Tracking Systems - '''Need to decide on tracking system.''' *** Cell Phone Tracking - Has issues, '''needs replacement'''. No longer acceptable as a viable tracking system per Brimstone and Bill Brown. **** Cold Test In Freezer - Test done uninsulated on phone trying to find a cell tower and recording and broadcasting GPS coordinates. Revealed a '''supplemental battery pack is required.''' First test had the battery last for 3 hours, need an hour margin for a 2.5-hour flight. Therefore batteries need to run for at least 3.5 hours. *** WhereAVR - '''Under evaluation'''. Brimstone and BendersGame have been looking into it as a tracking device. *** Ham Radio Beacon - '''Recommendation from Bill Brown''' as a tracking device that would fit our goal for a $150.00/vehicle budget. ** Secondary Tracking Systems - '''need to develop secondary tracking systems'''; install a radio chirper, flashing lights and an audio beeper on payload, paint the payload and parachutes international orange and install an international orange streamer. Set up a ground-based antenna to find the chirper. ** Tracking Test - '''Pending''' * Recovery ** Parachutes *** Cold Test - '''Not Yet Done'''. Cold soak them with dry ice (-109.3°F or -78.5°C) and see how well they perform in a weighted drop test. Dry ice is available at most grocery stores. *** Drop Test - '''Passed'''. A test with a 2 lb test weight and a drop height of ~150' was successful. * Lifting Hardware ** Lifting Gas - '''Ready'''. From J&M Cylinder in Hartselle, AL. Will be purchased and delivered on launch day at launch site. === Flight Equipment List === ==== Must Need ==== * Balloon - Only for 4/11 launch. * Lanyards to link payload and balloon ** 50 lb SpiderWire Line * Recovery ** International Orange Streamer ** Foam Block ** Labels with our logo, organization name, and 'who to call if found' contact info. * Payload ** Photography *** Digital Camera *** Memory Card *** Battery Chargers and/or fresh batteries for all the above ** Thermal *** Bubble Wrap *** Clear sealable ziplock bag *** Clear Packing Tape * Tools ** Duct Tape ** Foam-Safe CA ** CA Zip Kicker ** Exacto Knife ** Scissors ** Tarp ** Broom or brush ** Archoring weight (at least 20 lbs) ** Measuring tape (the kind for tailoring) ** Black Sharpie Marker ** Rubber Gloves * Recovery ** Binoculars ** Handheld GPS (preferably one for geocaching, not an automotive GPS) * A Big Van ==== Optional ==== For the 4/10 launch, tracking, lifting and recovery hardware will be provided by UAH and Bill Brown. For the 4/11 launch, tracking and recovery hardware and lifting gas will be provided by Bill Brown. Therefore, our equipment for them on each respective window are optional. * Lifting Gas * Recovery ** Parachutes * Payload ** Tracking Systems *** Cell Phone *** Supplemental Battery Pack *** Laptop w/ internet connection to [http://the.narro.ws/mologogo/ tracking website (http://the.narro.ws/mologogo/)]. *** Radio Chirper *** Yagi Antenna & Reciever *** Audio Beeper *** Flashing Lights *** Battery Chargers and/or fresh batteries for all the above === Pre-Flight Checklist & Flight Procedure for 4/10 and 4/11 Windows for Test Payload === * Developed on 4/9. === Flight Notes - 4/10 (4/11 Flight not Necessary) === * BendersGame, Brimstone, DraesDraco, Hanyan & Spacefelix were at the flight test. Spacefelix got to follow the tracking and recovery team, the rest supported from the ground station. ** Lessons Learned from Flight: *** BendersGame: **** Positives: Nothing lost. **** Negatives: Nothing worked. **** Camera: Somehow stopped taking pics while still being packed. Need to determine if this was because of unintended button pushing or if it was because of too much flipping and turning while packing. The way it works with CHDK is that the shutter button starts and stops the script. For human convenience, the shutter buttons have a slightly higher profile, making them easy to click - and it is entirely possible that a zip tie dug into it once, and that caused it to pause the script. We need to find a way to package the camera such that none of the elements are pressing into any buttons. An ideal solution would be a foam enclosure of just the right size that we seal up after setting off the camera. I wonder if there is a way of doing this. **** Tracking / Cell phone: Stopped working even as we were packaging, but even if it had worked initially, we have no idea how it will hold up later on. I think everyone is in the favor of ditching the camera and going with radio chirpers. We need to investigate into this. Another thing is we need to make sure that the tracker keeps going for several hours, in case something goes wrong and our payload gets towed to another place. Even if it chirps once every 30 mins after the first few hours, we will at least have a general idea of where it is going. I am not exactly sure what the story for today was, I think Ethan can fill us in on the details. **** Packaging: The foam board backing is not a bad idea, but I think we need to pair it with something more structural for a standalone launch. We can even string them up separately like the way they did to the payloads today, that way we can use the best packaging for each module without compromising the other ones. It would also be nice to work out a design such that we can pre-assemble parts and put them together with relative ease once we put in the main components - since there really is no way around having to activate components just before the launch. I guess we should aim for a build time less than what it takes to inflate the balloon, so we can start as the balloon is being inflated, and have everything ready to go as by the time the balloon is ready. **** Component coupling: After today's experience I'd say that we want any component to rely as little as possible on any other component, to avoid catastrophic failures. We were not planning on any nonessential coupling any way, but I figured it was worth repeating. **** Overall, I think it was a good learning experience. It would have been nicer if at least the camera had worked, but this is at least much better than losing the payload without knowing that the camera had stopped working too. So all in all, given that both of our components failed, this is possibly the best outcome we could have had. We'll at least know much better when we send out our own standalone payload. Saved us a fair amount of money too. *** Spacefelix: **** When the GPS device says it is at a specific location, due to position update delays, that could mean the position 15 minutes ago. So it is essential that you must not head towards the last position update, but wait for the payload position to become fixed before attempting recovery. It would also benefit us to have a GPS on the tracker and a GPS on the balloon so their positions are known to base station people. Altitude, speed and heading reporting is also helpful for determining the target's positions and what is happening to them. **** Along with cell phones, ham radios will help with communication. **** GPS is not 100% accurate. A reported position could mean the payload is within 100 feet of defined position. Also, the more cliffs/obstructions you have around you, there will be less GPS satellites received and GPS accuracy drops. **** Recovery is not always ideal. The payload can land in rough terrain and require you to do tree-climbing, rock/mountain climbing and/or hiking. Be sure to wear/prepare gear for such an expedition. The trackers typically brought with them rope and ladders to reach such hard places. **** Bring a driver's GPS (TomTom, etc.), a hand-held GPS and some kind of close-range tracking. They will complement each other for different phases of the search (driving there, homing in and looking around the brush). You can use these to home in to the position of the payload's reported GPS if you are using GPS tracking. **** Not all roads to the payload show up on the GPS and offroading is sometimes a must. Use off-road capable vehicles and bring a detailed map of the region of terrain and roads so you can find a path. **** The locals are really quite friendly and familiar with balloon tracking, but be sure to respect private property lines and ask permission before entering. Also, beware farm animals/dogs/bulls. You do not want to enter their territory during a search. **** Bill Brown may allow us to piggy back again. We'll have to organize it with him. **** Otherwise, our payload mostly stayed on and functional. When I picked it up, the phone was still on, but the camera had shut off. (Batteries were okay and full for both). The software is the issue as the tracking application on the phone shut down in-flight and the camera script stopped working due to an inadvertent button trigger.

Return to HSIS/1st Flight.