Tag Archives: Hackerspace

Transparency Means Sharing Failures and Successes

Maureen and I had lunch with Jerry from Maui Makers and the Hackerspace Space Program a couple of weeks ago.  We talked about a number of things including Open Design Engine, Makerspaces (which led to a brief tour of Dayton Diode), and Open Source Hardware.

It was our conversation around open source hardware which had me thinking back to our meeting days later.  We started off talking about the usual stuff:  licensing, the new Open Source Hardware Association, and of course we talked about open source spaceflight.

But then, sitting there in a Panera Bread over coffee and snacks, the conversation turned toward questions we don’t always address when talking about open source hardware.  Questions like:

  • What should happen to abandoned projects on sites like Open Design Engine?” – Well, we should keep them up for others to learn from or fork into new projects, which is what Source Forge does.
  • But won’t that eventually lead to lots of incomplete projects?” – Probably, which on the surface sounds like a “bad thing”, especially if there are many more abandoned projects than completed or active ones.
  • And what if the reason the project was abandoned was it just didn’t work?  What if it was a failure???” – People really don’t like to share their failures…
  • But, wouldn’t you want to know about the things that didn’t work so you don’t have to discover that for yourself?” – Well, yes. . . Of course. . .

And then it happened:  the light bulb flashed on, and we started talking very excitedly about science, engineering, publishing, and how hardly anyone writes about their failures.  They only share their successes.  In fact, if someone were to publish one of their failures, their peers would stare at them with bewildered expressions and ask “What are you thinking?”

It was Maureen who put it best, pointing out that we need to change the culture so people’s reaction becomes “What do you mean you didn’t share your failure?!?!

In that spirit, allow me to present an update on Mach 30’s first open source hardware project, including the good with the bad, so we can all learn from the progress Mach 30 has made.

Shepard Test Stand Update

One concept for the Shepard Test Stand

Things have been very busy at the Shepard Test Stand.  Since announcing the project in May, we have completed the requirements analysis, the block diagram, and are working steadily through Shepard’s design.  That’s pretty good news.  We also submitted two Shepard related presentation proposals to the Open Hardware Summit.

The first submission was a plenary session presentation looking at the engineering process used to develop Shepard and the instrumental role Open Design Engine played in the process.  The second submission was a demo of the Shepard Test Stand.   We were disappointed when our plenary presentation was not accepted, but were pleased to be included as one of the demo projects.

So Shepard has had its share of successes, but what about the failures?  Where have things not gone as planned?  The most significant challenge for Shepard is our schedule.  We are more than a month behind, and we now have a confirmed deadline of September 27, 2012 to conduct a public demonstration of the test stand.  This gives us just short of two months to complete the design (which is mercifully nearing completion), assemble, test, and document Shepard.  That is a tight time frame, especially given our work to date.

So, how did we get so far behind schedule?

I see two driving factors.  First, we were probably a little aggressive in the scope of Shepard, and in the time we allotted ourselves to complete the project–especially when you consider this was our first open source hardware project.   Second, we split our focus between Shepard and our work on the Far Horizons Project High Altitude Balloon.  Our group of volunteers is still pretty small, and many ended up working on both projects.  With limited time, something had to give.  At the time, the deadlines associated with the High Altitude Balloon (HAB) launch meant that Shepard’s timeline that had to give.

Still, with the current round of development work on the HAB basically wrapped up, we will be turning our full attention to the Shepard Test Stand.  Hopefully, we can find a way to get caught back up and be ready for the Open Hardware Summit.

Only time will tell.

Up, Up, and Away: Live(ish) coverage of High Altitude Ballooning

Today’s the day!

Mach 30 President, J. Simmons and volunteer, Jeremy Wright are in Chicago to begin documenting Open Design Engine‘s first High Altitude Balloon project.

This project is a partnership between Adler Planetarium‘s Far Horizons Project and Albuquerque’s Hackerspace, Quelab.  Adler is providing the design for the balloon, Quelab will build and launch the balloon, and Mach 30 is providing project hosting space on Open Design Engine and project coordination.

As an added bonus, Mach 30 will also be participating in this weekend’s launch.

Watch this space throughout the weekend for new videos, updates and more!

Design Meeting–Live!

You can watch the first design meeting live here–unless the meeting is over, then you should be able to see the video playback.


A small sample of the photos we took on the trip.

Get Involved!

Tweet your questions and comments about the projects with the hashtag #M30AdlerHAB we’ll answer as quickly as we can.  You can also leave comments below.

For more detailed information about the project as it progresses, watch the project page on ODE, and follow the updates on meeting minutes here.

Podcast Round Up

Image by Silveira Neto via Flickr

We’ve been stepping up the number of conferences we attend at Mach 30 because we’ve found them to be a great way to spread the word about our organization and to connect with some really great people.  Some of those people are connected with podcasts, and we have been fortunate enough to be invited to do several interviews over the last few months.

Just last week I was interviewed on the Public Knowledge In the Know podcast.  I met the interviewer through contacts from the Open Hardware Summit.  We talked about Open Design Engine, the genesis of Mach 30, and what lies ahead in 2012.  As always, it was a pleasure to have the opportunity to share the Mach 30 message with a new audience, and I am very thankful to Public Knowledge for inviting me.  You can listen to the Public Knowledge podcast here (the Mach 30 portion of the interview starts around 18:47).

Back in November, Evadot had me on their podcast.  A contact from the hackerSPACE Workshop mentioned Mach 30 to Evadot, and not long after we scheduled the interview.  We talked about open source spaceflight, the challenges of ITAR, and Mach 30’s approach to those challenges.  You can listen to the Evadot podcast here.

Finally, in October, Greg Moran, Mach 30’s Vice President, and I were jointly interviewed on the Open Hardware Junkies podcast.  Greg and I met the gentleman who runs this podcast during lunch at the 2011 Open Source Hardware Summit.  We spent much of the podcast discussing the role open source hardware plays in the Mach 30 mission and the tools Mach 30 is assembling in support of open source hardware.  It was especially fun to have Greg along for the interview.  I think it is great when we get a chance to bring our different styles of presenting Mach 30’s mission to the table together.  You can listen to the Open Hardware Junkies podcast here.

I’m looking forward to the spring when the next season of conferences gets rolling so we can meet even more people (those associated with podcasts and otherwise) to share the Mach 30 mission and 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.

Project: Hackerspace tour of the mid west

Purpose:  Community building, Getting our name out, Capacity demonstration/test

Description:  Mach 30 board members schedule visits to various hackerspaces.  These visits allows Mach 30 to advertize to their target demographic (makers, space enthusiasts, etc.).  Also the concept of bringing some type of demo project that would involve participation from the hosting space’s members.

A similar tour was done by Noisebridge member Mitch:http://blog.noisebridge.net/2010/08/04/mitchs-midwest-workshop-tour-of-h…

Possible Destinations:

OCD — Detroit, MI
Mt. Elliot Makerspace – Detroit, MI
I3 — Detroit, MI
A2 MechShop — Ann Arbor, MI
AHA — Ann Arbor, MI
LVL1/Actors Theatre – Louisville, KY
LVL1 — Louisville, KY
Hive13 — Cincinnati, OH
BloomingLabs — Bloomington, IN
Arch Reactor — St. Louis, MO
KC Mini Maker Faire / CCCKC — Kansas City, MO
Quad Cities Co-Lab Hackerspace — Quad Cities, IA/IL 
PS:1 — Chicago, IL
Madison BarCamp — Madison, WI
Sector67 – Madison, WI

Project ideas:

  • Weather balloon camera to space:
    • Set up in the morning (photo document the days activities)
    • Launch balloon (photo document the days activities)
    • Track progress throughout the day (photo document the days activities)
    • Enlist the help of members to chase and recover camera package
    • Download pictures and compile presentation by adding todays photos to existing template
    • Evening briefing about Mach 30 and include pics from todays acticvities
    • Catered Dinner?
  • Portable satelliete tracking ground station
    • Set up ground station (photo document the days activities)
    • Determine the availbility of trackable satellite passes (photo document the days activities)
      • viable passes: demo the tracking system (photo document the days activities)
      • if there are no viable passes, run a pre-recorded simulation
    • Compile presentation by adding todays photos to existing template
    • Briefing about Mach 30 including pics from todays activities
  • Demo firing of hybrid rocket engine
  • Other ideas?