Two weeks is a HUGE amount of time considering we launch every month. Having a list of things that *might* be on board by that time, and their likely weights (sans possible cables...) might not be a bad idea, though.<div>
<br></div><div>That was the *beta* launch page. We're doing greek letters. So the next will be gamma then delta.</div><div><br></div><div>Christie<br clear="all">_______<br>"We also briefly discussed having officers replaced by very small shell scripts." -- Noisebridge meeting notes 2008-06-17<br>
<br>The outer bounds is only the beginning. <a href="http://www.flickr.com/photos/genriel/sets/72157623376093724/">http://www.flickr.com/photos/genriel/sets/72157623376093724/</a><br>
<br><br><div class="gmail_quote">On Wed, Mar 31, 2010 at 11:03 PM, Albert Alexander <span dir="ltr"><<a href="mailto:albert.alexander@gmail.com">albert.alexander@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I strongly endorse having a weigh-in two weeks prior to launch. No changes in mass after that. That'll give us time to actually assemble and test the bus.<div><br></div><div>I did a top-down checklist on the Bravo launch page, but we need software test procedures to be added.<br>
<br></div><div>I think thermal control is a must for next launch. I thought it was silly to launch this time without fixing last launch's failure point. I'll parse Alpha's temperature data this week to get a starting point.</div>
<div><br></div><div>Also I am totally serious about sending a small animal up on Delta launch (not Charlie. Is the next launch Charlie? Or is it just the "real" Bravo?).</div><div><br></div><div>A</div><div><br>
<div class="gmail_quote"><div><div></div><div class="h5">On Wed, Mar 31, 2010 at 10:29 PM, Christopher Lincoln <span dir="ltr"><<a href="mailto:cclinco@gmail.com" target="_blank">cclinco@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">
Meeting notes from 03.30<br><br>Suggestions for improving launch quality and efficiency<br> - Need a standard process for setting up and testing electronics. This process must be well documented<br> - Preflight check list.<br>
- Battery check<br> - Have “Yay or Nay” call of the Tuesday meeting before the launch.<br> For a “Yay” call to be made, every critical component must be completed and tested.<br> - A full check list of what is going up with this launch and their dependencies<br>
- Mark the tank as we open it, to alleviate confusion as to which one was used.<br> - Always take a second (back up) tank to each launch<br> - create wiki pages of each payload item, including set up instructions. (list of needed pages are on the bottom of this page.)<br>
- Provide better communication for the drive out of the launch site<br> - locate stores in the area that can provide forgotten items like batteries and helium<br><br><br>List of tasks that we should do before the next launch<br>
- Test different types of batteries in the freezer (both types of batteries and competing brands)<br> - acquire a bathroom scale to weigh the helium tanks with.<br> - Purchase condoms, extra large<br> - the cannon IS1100 stopped taking pictures shortly after being turned on, probably battery related, but we should test to make sure.<br>
<br><br>Ideas for next launch<br> - One battery grid to rule them all! This would consist of 2 battery systems that connected just prior to the component giving a back up system should one fail.<br> - add solar cells to the outside to the payload to test energy received as we go up. We can use the datalogger to store the information.<br>
- Use a droid with debian installed (Chris has one) to feed data from a USB hub that had has several web cameras hooked up and save the data out to a USB harddrive. Alternatively we could also use a beagle board (Nils has one).<br>
- Attach LED blinkies or stroke lights (from disposable cameras) to the end of the antenna support arms.<br> - Add a high pitch buzzer to the payload bus to help locate it<br> - add brightly colored inflated condoms (balloons will work also) to the payload so that they will float above the final resting place, assisting in locating it.<br>
- Add a video camera, and stream it's feed over a ham radio to a base station. This would use a NTSC broadcast. This has the potential to be expensive, so Chris will gather - a cost estimate for this (both dollar and if possible weight)<br>
- make the video camera steerable. Even outside of the flight this would be usable as we could then be able to see the area where the payload landed before having to walk - there. <br><br><br>Ideas talked about, but decided to be considered independent of the core Spacebridge concept<br>
- Generating Hydrogen quickly and cheaply. While awesome, it's to dangerous and inconvenient for us to focus on at the moment.<br> - UAV. Again awesome, but is a large enough project to be considered independent but closely related and potentially intersecting Spacebridge.<br>
<br><br>Wiki pages that need to be created and maintained.<br> - Radio, with set up instructions
<br> - Radio Antena (dipole)
<br> - GPS
<br> - Packet Tracker
<br> - Open Tracker
<br> - G1, including applications used and set up intructions
<br> - Canon A700 Camera, including CHDK, script, battery limitations, SD card limitations and set up instructions
<br> - Canon IS1100 SD Camera, including CHDK, script, SDHC card limitations, instructions
<br> - Payload Bus
<br> - Icrais program
<br> - Android APRS<br>
<br></div></div>_______________________________________________<br>
Space mailing list<br>
<a href="mailto:Space@lists.noisebridge.net" target="_blank">Space@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/space" target="_blank">https://www.noisebridge.net/mailman/listinfo/space</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Space mailing list<br>
<a href="mailto:Space@lists.noisebridge.net">Space@lists.noisebridge.net</a><br>
<a href="https://www.noisebridge.net/mailman/listinfo/space" target="_blank">https://www.noisebridge.net/mailman/listinfo/space</a><br>
<br></blockquote></div><br></div>