About Lenore

Co-founder of Evil Mad Scientist Laboratories

From the mailbag: Fun soldering

Eric wrote in to say:

It was fun. It was fun to build the Larson Scanner. It was fun because I successfully put it together and it worked as designed. It was so fun I’ll do this again!

In the mid 70′s I attempted to construct a Radio Shack short wave radio kit with a soldering gun. That’s right, I used a soldering gun. Believe it or not, it worked … as a battery heater upper.

Thank you for the helpful instructions and well designed kit. It’s nice to know that 40 years after my last kit, I can drop the battery killer nickname.

The Power of the Digi-Comp II

Last fall, we built an oversized Digi-Comp II for MIT, which we’ll be posting about in the near future. Today, MIT computer science professor Scott Aaronson published a short “paperlet” about the computational capabilities of the Digi-Comp II on his blog, Shtetl-Optimized:

…it’s amazing that such a simple contraption of balls and toggles could already take us over the threshold of universality.  Universality would immediately explain why the Digi-Comp is capable of multiplication, division, sorting, and so on.  If, on the other hand, we don’t have universality, that too is extremely interesting—for we’d then face the challenge of explaining how the Digi-Comp can do so many things without being universal.

Pen tests for drawing machines

Jenslabs has published a thoughtful and thorough evaluation of a number of currently available rollerball and gel pens. He tested them using his Circlon machine.

One thing that anyone who as ever built a drawing machine realizes, is that to get quality results you need a quality pen. There are millions of pens out there, but after a little trial and error I realized that rollerball pens or pens with gel ink are the best pen types for my machine. Both rollerball and gel ink pens use a water based ink that is less viscous then the oil based ink used in ballpoint pens. The Circlon machine sometimes move very fast, so the pen has to be able to release enough ink to make solid lines even at high speed.

This is an excellent resource for folks with other drawing machines, such as Egg-Bots and WaterColorBots. We’ve linked to it from our page about choosing pens for the Egg-Bot as well.

LED Robot Sign

Krummrey shared an LED Robot Sign tutorial on Instructables using one of our original Peggy boards. (Peggy 2 would work for this, too.)

I don’t solder the LEDs in. That way I can just pull them back out and make a new sign when I get tired of the current one.

That big pile of LEDs looks like so much fun! He also posted some more sign designs at the end of the instructable.

Electro-Kistka: Alternate In-Place Egg Dyeing Technique

After seeing our recent post on dyeing in eggs in place with the Eggbot, Ragnar posted instructions in the forums for an alternative egg dyeing technique.

It involves pre-installing a plastic dyeing bag at the time of positioning the egg in the Eggbot. Full instructions (with more photos) are in the forum post. Thank you for demonstrating this technique, Ragnar!

Women in the Maker Movement

In honor of National Women in Engineering Day, the Make blog is profiling women in the maker community this week, including me!

…this week we’d like to bring you profiles on women who are roboticists, artists, designers, programmers, and makers of all kinds over the next few days, and we’ll be making an effort to make sure that the women in the maker movement get their fair share of the spotlight as we build our maker community in the future.

Open Discussion: Best Practice for Mislabeled Open Source Projects?

non-oshw

In looking around for examples of great open source hardware projects, we came across an unexpected number of projects and products labeled as open source hardware that, upon closer inspection, actually turn out not to meet the definition. Often, they’re using an inappropriate license— typically a “non-commercial license,” which is not only unenforceable but explicitly incompatible with open source values. Sometimes, they haven’t released the design files. Sometimes, a person has apparently misused the term “open source” to mean “closed and proprietary.” And sometimes you might see the open hardware logo used without any substance to back it up.

But what (if anything) can or should be done about it? We’d like to solicit your input as to the best ways to approach this problem.  Perhaps there are not any easy answers.

As a baseline, we think that it’s important to address the problem, and to do so earlier rather than later. To mislabel a product for sale as open source hardware may constitute false advertising, illegal in the US under state and federal law. In noncommercial projects where nothing is for sale, misusing the terms may help to set precedent that can damage the community’s understanding of open source. For instance, if enough people see non-commercial licenses on things labeled as be open source, they may assume that it is acceptable.

If you happen to know someone behind the project, you might consider contacting them directly to start a dialog about what it means for something to be “open source.”  Or, you could (hint hint hint) send them a link to this article, letting them know that you found it interesting!

But, what if you don’t have any personal connections to the people involved? It’s certainly not as easy. Sometimes you can initiate a dialog with a company, perhaps by asking about their design files or licenses. At the other end of the spectrum, people sometimes bring up options like public shaming. In our view, shaming is harmful to the open source community, and should be considered a last resort akin to violence. Rather, we as a community need to work towards positive ways to nudge people toward doing the right thing.

Please let us know what you think: what should you do when you come across a project mislabeled as open source hardware?