Category Archives: Mach 30 Projects

Introducing the Shepard Test Stand: Mach 30’s first Open Source Spaceflight Project

by Jeremy Wright, Innovations Technology Solutions, LLC

[Editors Note:  I’ve been asking you to be patient on the hardware front for years now, so believe me when I say words cannot capture how excited I am to introduce you to Jeremy Wright–a new Mach 30 volunteer and major contributor to our very first open source spaceflight hardware project.  Thank you Jeremy for taking us over the breach–and thank you, patient reader, for sticking with us through the “boring” parts.]

Shepard Test Stand Block Diagram

Mach 30’s Shepard Test Stand project has contributors spread over 4 U.S. states and 2 different time zones, so making sure that everyone gets a chance to leave their mark on the project can be a real challenge.  Add to that the fact that we’ll not only be exchanging ideas, but also things like drawings and source code, and the challenge gets even more interesting. This kind of collaboration is possible because of what Mach 30 is doing through the Open Design Engine.

On Shepard, we’ve started this collaborative process in the project’s forums and wiki by working on the why, who, and how questions that will guide us through the rest of the design process. These are seemingly simple questions like:

  • “Why are we building this?”
  • “Who’s going to use this?”
  • “What features does it need to have?”

However, without solid answers to these questions we run the risk, as contributors, of not all pulling in the same direction. As we head deeper into the project, these answers are being turned into a list of requirements that will keep us grounded and focused throughout the life of the project. That way we’re all on the same page, and when we get to the more exciting tasks of building and using the test stand, we’ll have our best shot at hitting the target. These requirements will start to pay off right away by informing the creation of the system block diagram, which is our next step.

If you haven’t yet, swing by opendesignengine.net and look over the Shepard Test Stand project. ODE will be moving into public beta soon, and we’d love to have the help of anyone who’s interested in moving humanity toward a space-faring future.

In short, “ad astra per civitatem” – to the stars through community

Building high altitude balloons and hacking video cameras

Image by blackrazorus vis Flickr

In my last post, I proposed a partnership between Adler Planetarium, Dayton Diode, and Mach 30 to build and launch open source high altitude balloons in Dayton, OH.  I am happy to report the project has a “go”.  We have two volunteers from Dayton Diode who want to work on the project, and Ken at Adler Planetarium received “enthusiastic approval” for the Dayton Diode/Mach 30 crew to participate in Adler’s December launch.  Ken is also beginning to recruit volunteers in Adler’s Far Horizons project to gather and assemble documentation for posting on Open Design Engine.  I will continue to post updates on the project as they become available.

Our friends at Adler Planetarium also asked us for some technical assistance on another project, and I wanted to pass on their request.  Ken is working through the development of a project dealing with asteroid occultations and is trying to figure out if there’s a way to hack an off-the-shelf video camera to be able to capture 60fps video and record that video with lossless compression.  Ken is familiar with using CHDK to hack digital still cameras, but neither of us have any experience modifying video cameras.

This is where you come in…

Do you or someone you know have experience modifying digital video cameras?  We want to hear from you.  Leave a comment or send us a message.

ad astra per civitatem

Attending the hackerSPACE Workshop

This weekend Josh (a member of Dayton Diode) and I had the great pleasure to attend Kentucky Space‘s hackerSPACE Workshop.  The hackerSPACE workshop, led by Bob Twiggs co-creator of the CubeSat standard, was an introduction to CubeSats for hackerspaces, entrepreneurs, and educators.  In addition to the formal presentations, there were a number of group suggested breakout sessions including ones on educational outreach, open source CubeSats (of course, I suggested this topic), working with Amateur Radio operators, and operating high altitude balloons.  I am very happy to report the open source CubeSat topic generated quite a bit of additional conversation and opened the door to several partnership opportunities.

One such opportunity involves designing, building, and operating high altitude balloons.  During Mach 30’s strategic planning for 2011, the Mach 30 board decided to start its CubeSat development efforts by first building high altitude balloons.  High altitude balloons offer many of the same design, fabrication, and operation challenges as CubeSats, at a fraction of the cost, making them ideal “kites“.  And, it turns out, there are several high altitude balloon programs near Ohio to partner with, as we learned from the high altitude balloon breakout session at the workshop.  These programs include:

It turns out Josh and I sat next to Adler Planetarium’s Ken Walczak.  Ken and I talked at length about the Far Horizons program and launching high altitude balloons.  It turns out Adler Planetarium has been looking for a way to share the designs and procedures for their high altitude balloons in support of their educational mission.  It just so happens, Mach 30 has a website for sharing open source hardware projects, and as mentioned earlier, a desire to build its own high altitude balloons.  There has also been talk at Dayton Diode about building a high altitude balloon as a group project just because it would be cool.

Sounds like a great partnership opportunity to me.  Here’s how I see it working.  Mach 30 would provide project coordination, funding, and hosting (on Open Design Engine).  Dayton Diode members who are interested in a high altitude balloon project would volunteer their time to build and operate the balloon.  And Adler Planetarium would provide the experience (in the form of plans, procedures, and training).  Ken from Adler has already expressed an interest in this proposal, and believes he can arrange for a live training opportunity for Dayton Diode members at one of the upcoming Far Horizons launches (the next one is in December).  And Mach 30 has funds allocated for a high altitude balloon project.  And, I am cross-posting this blog post on Dayton Diode’s blog to gauge their interest.  More details to follow as things move forward.

What He Does When I Leave Town…

As we observe the last shuttle mission with a mixture of sadness and celebration, I am inspired to share my most recent and personal brush with rocketry…

Last month I was the Matron of Honor in my best friend’s out of state wedding. It was a lovely wedding and a good trip. When I returned home to my happy pets and husband, I asked him what he did while I was away.

Him: “Oh, you know, work, laundry, dishes, hung out with Scott… I need to buy a few more rockets though.”

Me: “Rockets??!?!?!!”

Him: “Oh, yes. I built some rockets while you were gone.”

Me: “(stunned silence)… Built. Some. Rockets… !??”

Now my dear husband is not a rocket scientist, but he has dabbled in flying RC Airplanes a good bit, so I suppose I should have seen this coming. He only built “some little ones… well, ok, and a medium one too.” If he builds some more and launches them just so, meeting certain criteria, he can get his Bronze Certification with the National Association of Rocketry. Don’t I want him to be be certified to launch rockets?

Who could say 'No' to this?

After six years of marriage, I am somewhat accustomed to his hijinks, so I didn’t hit the roof or use his full name at him or anything like that. I first asked where he might have launched these rockets, what gave him the idea and if he’d hurt himself or others. Turns out, he had been very safe and responsible and launching rockets is really not that big a deal (“NASA does it all the time”). He got the idea from  J.’s blog post. J. is a rocket scientist.

My husband then took my inquiries to mean I wanted to know (much) more about the arts of rocketry and regaled me with way more technical detail than I was prepared for, including gluing techniques, motor assembly and sizes – “A is a small one and G is crazy big with all the letters in between. They are measured in Newtons of force so basically higher letters equal more power.”

Me: “Like bra sizes?”

Him: “Um, yes…”

Apparently, you can get the smaller rocket starter sets for around $25-30 and they have little parachutes or streamers so you can get them back in one piece and reuse them. There is a whole instruction manual here  for those of you who like making things go fwoom!

success!

If you would like to help insure that all surprise spousal rocket encounters go as well as this one did, you can donate to Mach 30 (creators of the Rockets 101 Manual) here,

Or share the Rockets 101 Manual with your friends who may be at a high risk for trying to shoot things up into the sky,

Or subscribe to Mach 30’s newsletter for more space-y, science-y, open source-y and occasionally entertaining news.

Rockets 101 Update: A story of preparation and clever hacks

Yesterday was the last launch day of the season at TORC (it turns out the farmer needs his field back to grow corn during the summer, go figure).  So, it was my last chance to test out the draft Rockets 101 Manual content under live conditions (and to get my NAR Bronze flights certified while I was at it).  I would love to be able to report that everything went according to plan, but that just is not the case.  However, as is often the case, I think the lessons learned from the complications that came up yesterday are far more valuable than those that would have come out of the day just going according to plan.

I spent the night before reviewing the requirements, packing my rockets and materials, and updating the course manual.  When I got to the field, I decided to start with the non-timed flights (in testing the timed flights were the harder ones to achieve success on, and I wanted to get some early momentum going).  As expected, my first two flights went off without a hitch, and allowed me to quickly get half way through the Bronze certification objectives.  The details of the flights are as follows:

  • “D” size or larger flight

    Rocket: Big Daddy

    Preparation: 7 squares of wadding

    Motor: D12-3

    Notes: Successful flight, achieved Bronze objective.  However, there was some minor melting of the parachute.  Should increase wadding on next flight of this rocket.

  • 2-Stage flight

    Rocket: Aztec

    Preparation: 3 squares of wadding, streamer recovery

    Motor: B6-0/B6-4 (taped together and friction fit with tape per kit instructions)

    Notes: Successful flight, achieved Bronze objective.  Some minor dings to the booster stage.

With two great flights under my belt I moved on to the first of the two timed flights, the 30+ seconds streamer recovery.  The spec’ed rocket for this flight is an Estes Hi-Flier.  This rocket always performed well in testing, so I felt confident it would pass the requirements.  There is just one minor detail I failed to consider.  The Hi-Flier is a very small rocket, and the launch site is a VERY large cornfield.  I’ll let the flight log below tell the rest of the story.

  • 30+ sec streamer recovery flight

    Rocket: Hi-Flier

    Preparation: 3 squares of wadding, streamer recovery

    Motor: B6-4

    Notes: Flight lasted 43.6 sec.  Rocket landed beyond line of sight.  Over an hour of searching failed to turn up the rocket.  Bronze certification requires recovering the rocket; objective not met.  Check with Greg to see if he used a B6-2 for his flight.

So, this was a problem.  First, I had failed to meet the requirement for the third mission.  Second, the Rockets 101 Manual calls for using the Hi-Flier for both duration flights.  I now had a choice to make.  I still had a B class motor rocket I could fly, namely the Aztec upper-stage.  But testing had shown time and again that most rockets could not meet the streamer recovery times.  So, I could either fly the Aztec upper-stage in an unlikely attempt at the streamer flight or go home.

I decided to go ahead and try the Aztec.  Worst case is I lost it, too, but I already had my 2-stage flight certified, and it is not a very expensive rocket.  Turns out it missed the time by 3.5 seconds, as shown in the flight log below, but that is not the end of the story.

  • 30+ sec streamer recovery flight

    Rocket: Aztec Upper-Stage

    Preparation: 3 squares of wadding, streamer recovery

    Motor: B6-4

    Notes: Flight lasted 26.5 sec.  Rocket landed close to launch site.  After the flight, another NAR member at the site asked if the rocket had a motor clip or used tape to friction fit the motor.  I answered it used tape, and he replied, try it without the tape so the motor will eject and lighted the returning rocket.

Talk about a clever hack.  The suggestion from the observing NAR member to simply let the motor eject so the rocket would weigh less on its descent was brilliant.  And it was just what I needed to get the last few seconds for the streamer duration flight.  So, quick turn around and then I tried again.

  • 30+ sec streamer recovery flight

    Rocket: Aztec Upper-Stage

    Preparation: 3 squares of wadding, streamer recovery; motor inserted without any tape so there was very little friction in the fit.

    Motor: B6-4

    Notes: Flight lasted 33 sec.  However, the rocket landed further away and it took nearly 45 min to find it in the field.  Rocket was undamaged, Bronze certification requirement accomplished.

Finally, after nearly two hours spent on recovery operations, and some clever hacking, the first of the two timed trials was complete.  The last flight was actually a breeze.  I again flew the Aztec Upper-Stage, this time swapping the kit’s streamer for a 12 inch parachute.  I continued to exclude the tape from the motor mount.  I also chased the rocket while it descended so I would not run the risk of not being able to find it, and I was able to recover the rocket in just a few minutes.  However, this meant I did not know the duration of the flight until I got back from my recovery…  At which point, I learned it had flown for 76 sec, easily achieving the 60 sec requirement.  Woot!

  • 60+ sec parachute recovery flight

    Rocket: Aztec Upper-Stage

    Preparation: 3 squares of wadding, 12″ parachute recovery; motor inserted without any tape so there was very little friction in the fit.

    Motor: B6-4

    Notes: Flight lasted 76 sec.  Chased rocket down during descent.  Rocket was undamaged, Bronze certification requirement accomplished.

So, there you have it, all four requirements for NAR Bronze certification achieved in one day.  Based on the performance of the Aztec Upper-Stage, I think it is worth it to conduct some additional testing to see if it is reliable enough as configured to be the spec’ed rocket.  It would be very exciting to shave an entire rocket off of the build list for the Rockets 101 curriculum.

ad astra per civitas