Technically you can use this setup to make any kind of interactive ice luge.  But I used it to make a Trump head ice luge, so that’s what this post is about.  To be clear, when I say “Trump head ice luge”, I really mean, “Trump head spout on an ice luge”.  This isn’t a giant block of ice shaped like a head.

The central principle here is fairly straightforward.  There is a sensor that detects fluid.  When it detects fluid, it triggers 1) a random audio clip, and 2) a change in light color while the clip is playing.  My version played one of 45 random Trump clips and turned the lighting from the default orange to red for the duration of the clip.

Bill of Materials

- Wood and screws for the rack (I used some 2x4s and plywood)

- Lots of cardboard, newspaper, and trash bags (for the ice, more on this below)

- 1 Arduino

- 1 Adafruit Music Maker Shield 

- 1 liquid flow meter

- Tubing that mates with the flow meter (I just took the meter to the hardware store and wandered around the plumbing area until I found something that worked.)

- Funnel

- Clip

- 2 speakers

- Hot glue gun

- 4 NeoPixel Diffused 8mm Through-Hole LEDs

- A 3D printed head

- Wires and a power supply for the arduino.

- Audio clips

Making the Ice

This is going to take longer than you think.  Clear out space in your freezer and make a cardboard box that will fit.  The box will expand a bit with the ice, so make sure there isn’t anything built into the freezer wall (say, posts to hold racks) before sizing the box.  The box here was 2 pieces of cardboard thick and then wrapped in tape.  It was about 7 inches by 14 inches by 27 inches when all ways said and done.

Roll up the newspaper tightly. Use the resulting tubes to build a track into the inside of the box by taping the tube to the wall of the box.  This will create the channel in the ice luge.

Next line the box with heavy duty garbage bags.  Once you have done that, you can start filling up the box with water.  Depending on the size of your block, expect this to take at least a week.  A few tips:

- Chill the water before adding it to the box

- If possible, create a large block (still smaller  than the one you want to make) of ice to seed your full block of ice.  Put it in the box and then fill the box with water until the block floats. The water in the middle freezes last, so if that water is already ice things will go faster.  Plus the floating ice will suggest that you are creating enough outward pressure on the walls to get a nice groove.

- When water freezes, the ice floats to the top.  That means that even if the ice at the top of the box is solid, there is likely still water at the bottom/in the interior.

- Add enough water to push up against the walls of the box.  That will make sure that your channel is deep when you pull it out.

- It will take longer to freeze than you think.  Turn your freezer down as low as possible.

Eventually, if you are lucky and patient, you will have a block of ice.  When it is time to use the ice, just cut away the box and pull off the trash bags.  It is likely that bits of bag will be frozen into the block.  If you are lucky there aren’t that many.

Making the Head

Fortunately I did not have to model the head myself.  Thingiverse user digitalcoleman had already created a low poly Trump head and licensed it under a CC-BY license.  I downloaded it and used tinkercad to create the voids for the tubes, meter, and LEDs.  You can download my version here. 

If I had to do it again, I would have created shallow channels in the bottom connecting the spaces for the LEDs.  That would make it easier to connect them with the wires.

Note that if you print the model at scale it is a really long print.  Fortunately Andy at Open Factory hooked me up and printed it for me. Also note that printing it in a clear material makes the LEDs work much better.

The Code

You can download the code here (it’s final.ino.ino).  As noted in the header, I got a lot of help for it in the adafruit forums.  Hopefully the comments are enough to help you figure out how it works. If you are using everything I used, it should just work.  It should also be easy to find the lines to change the colors if that’s your thing.

You will also need to get your audio clips together.  I had about 45.  Label them as track001.mp3, track002.mp3, and so on and put them on the SD card. (There is no link to this on the musicmaker page, but here’s the tutorial for the shield).  The software will randomly pick a track to play every time. It will also know how many tracks there are, so you don’t need to worry about setting that variable in the code or anything.

Putting it Together

Here’s a wiring diagram (it only shows 2 LEDs but my final had 4)(also, when you are wiring the LEDs I had the flat side facing to the right):

I used a hot glue gun to glue the 4 neopixels into the voids at the bottom and then soldered them together. You can see how having channels between the holes would have helped here.  The fifth and sixth hole are for the mounting screws.

The wiring for the sensor can sneak out the back of the head as well.  Once you have that together, just put the tubes in the hole.  You can then mount it on a block of wood.  I found that the default angle for the head wasn’t quite right in my setup so I mounted the head on an angled block of wood.

Finally, you will probably want to mount the tube and funnel.  I designed a clip to hold it in place.  The file is on the github page.

Once it is all wired up, you just have to mount it onto the rack.  Assuming you did the wiring correctly it should be fairly straightforward.  Here’s what it looks like:

I found that even at a pretty loud volume the speakers weren’t quite loud enough for a party full of people.  About half way through I just plugged it into an amp with speakers.  Fortunately there is a headphone out on the MP3 shield so that was super easy.

Oh, and here’s what it looks likes:

This post originally appeared on the OSHWA blog.

Last month at the Open Hardware Summit we announced the start of the OSHWA open source hardware certification program.  Part of that program involved issuing unique IDs (UIDs) for each piece of registered hardware.  Since we knew that low numbers would be hot properties, we decided to wait until the end of October to assign them.  That allowed us to give every piece of hardware registered in the month of October a chance for the lowest possible number.

Today, thanks to the good people at random.org, we have assigned those UIDs to all pieces of hardware registered before the end of October.  We have also started assigning numbers sequentially for all pieces of hardware registered since November started.  You can see all of the registered hardware  here.

There were 60 different projects registered from 9 different countries.  Want to get your own UID?  Register here!

This post originally appeared on the Shapeways blog.

When a cheerleader wears her uniform, is she expressing her identity as a cheerleader or identifying herself as a cheerleader? And could the distinction ever even matter?

This is one version of the question that the U.S. Supreme Court wrestled with today. Its answers could have a big impact on how copyright interacts with 3D printed objects.

The Cheerleader Uniform Case Goes to Court

Today were the Supreme Court oral arguments in the Star Athletica v. Varsity Brands copyright infringement case, which you may remember as the case about cheerleader uniforms we’ve been writing about since lastyear. On its face, the case is about how and whether copyright should protect designs on cheerleader uniforms. We care about it here at Shapeways because it is really about how copyright interacts with objects that combine functional (traditionally not protected by copyright) and non-functional (traditionally protected by copyright) elements in one.

If you are thinking about licensing your 3D printed object or worried that someone is infringing on your work, the first thing you need to know is if the object is protected by copyright at all. The decision in this case could give us a single, clear rule to use in answering that question. Appropriately enough because this is Halloween, it will also be helpful for those of you who think about copyright in relation to costumes and cosplay.

Of course, while those larger questions linger in the backdrop of this case, the immediate question is about cheerleader uniforms. Specifically, it is about the designs on cheerleader uniforms.

As a general rule, copyright law views clothing as “functional” and therefore beyond the scope of copyright protection. In a nutshell, clothing is functional because it keeps you warm, dry, and not-naked. However, designs on clothing (think a flower print on a dress) can be protected by copyright. That is because the designs are not really functional, but rather separable aesthetic elements merely attached to the otherwise functional dress.

Why Are Stripes and Chevrons on Cheerleader Uniforms?

Much of the debate today was about the role of things like stripes and chevrons on cheerleader uniforms. Are they there for “expressive” (read: copyrightable) purposes so that the wearer can express her allegiance with cheerleaders? Or are they there for “functional” (read: not copyrightable) purposes so that the wearer can be identified as a cheerleader? And yes, this distinction also makes copyright lawyers’ heads hurt.

For a case about cheerleaders, there was a lot of discussion about camouflage in Court today. Camouflage as a design in a frame on the wall is probably protected by copyright. After all, on some level it is just an artful arrangement of colors that – at least in a frame on the wall – serves no obvious functional purpose.

However, if you print the same camouflage pattern on a shirt and pair of pants, it can suddenly have the very functional purpose of making it easier to hide in the woods. At that point the pattern would probably become functional and therefore – at least in the shirt and pants context – not eligible for copyright protection.

The stripes and chevrons on a cheerleader uniform can be thought of the same way. On a piece of paper in a frame on the wall, they are just an artistic collection of stripes and chevrons protected by copyright. On a uniform, they may serve important functional purposes: in addition to identifying the wearer as a uniform, they can make the wearer look taller or slimmer, or just reinforce various seams in the uniform itself.

Needless to say, there was also ample discussion of Duchamp, hanging shovels on art gallery walls, and what really constituted art.

What Does This Have to Do With 3D Printing Again?

Abstracted up a level, all of this discussion about putting parts of an object into functional and non-functional categories mirrors the analysis you would do to determine if a 3D printed object that is both functional and artistic would be protected by copyright.

In a previous post we flagged studiogijs’ birdsnest eggcup quattro as an easy example of this. It has functional (holding an egg) and non-functional (looks like a birds nest) properties. A rule coming out of the cheerleader uniform case could provide us with a rule to understand how – if at all – copyright might apply to the eggcup too.

What Happens Now?

It is always dangerous to make projections based on oral argument. It was pretty clear that at least some justices were wary of a decision that would pull all clothing into the world of copyright (at one point Justice Breyer worried that pushing copyright lines deep into clothing would “double the price of women’s clothes” for no real purpose). Many others struggled with how to draw the line between functional and non-functional elements of clothing.

It is no surprise that the Justices struggled drawing this line. Going into this case, there were at least ten different theoretical approaches that courts have used. Hopefully, the Supreme Court will come up with a single test that works for cheerleader uniforms, 3D printed objects, and everything in between.

We will find out once the written opinion is released during the first half of next year. Until then, you can read the transcripts or hear the audio of the arguments (don’t miss Justice Breyer – again – working to understand the relationship between clothing and the context by musing, “The clothes on a hanger do nothing, the clothes on a woman do everything.”)  And let me know if you have thoughts or questions in the comments below or on twitter @MWeinberg2D.

This post originally appeared on the OSHWA blog.

Today the Open Source Hardware Association is excited to announce the OSHWA Open Source Hardware Certification program.  The program allows hardware that complies with the community definition of open source hardware to display a certified open source hardware logo.  It will also make it easier for users of open source hardware to track down documentation and more information.  You can check out the program here, and keep on reading for some information about how it will work.

These companies and organizations have agreed to certify at least one piece of hardware by the end of this year.

Background and Purpose

Almost a year and a half ago, OSHWA announced its intention to explore the creation of an Open Source Hardware certification.  At that point, the open source hardware community had created a community definition of open source hardware and the open source hardware open gear logo.  Both of these were significant contributions to the growth in awareness around open source hardware.

By design, no one owns the term “open source hardware” or the open gear logo.  This allowed both the term and the logo to be widely adopted by the community.  However, it also created a challenge.  In many cases, creators would label their hardware as being open source and use the open gear logo without complying with the community definition.  This created confusion in the community where users were unsure what it really meant when something was labeled “open source hardware”.

The certification is designed to complement the existing open gear logo by bringing clarity to how the creator is using the term “open source hardware”.  Unlike the open gear logo, the certification logo is controlled by OSHWA.  In order to use the certification logo, a hardware creator must make a legally binding promise that their hardware complies with the community definition of open source hardware. That means that when users see the certificated open source hardware logo they know the hardware complies with the community definition of open source hardware.

In the summer of 2015, OSHWA asked the community a number of questions about how a certification might work and what kind of value it might bring.  By the 2015 Open Hardware Summit, those discussions had coalesced around version 1 of the Open Source Hardware Certification Specification.  In the year since, OSHWA has worked with the Juelsgaard Intellectual Property and Innovation Clinic at Stanford University Law School to turn that specification into a fully functional registration system.

The System

Starting today, you can register your hardware for free by certifying that it complies with the community definition of open source hardware.  The registration site –certificate.oshwa.org – has an overview of the process, the text of the license agreement for use of the certification logo, guidelines for how the logo can be used, a history of the certification process, an FAQ related to the certification, a form that allows you to register your hardware, and a directory of registered hardware that includes links to relevant documentation and information.

Upon registration, you will receive the right to use the certification logo and a unique identifier for the registered version of your hardware.

That unique ID has two components.  The first two characters represent a country code.  Open source hardware is a worldwide community, and the country code is an opportunity to recognize and celebrate that fact.  The remaining characters are numbers assigned sequentially based on when the hardware was registered.

The Importance of Your Contribution

One of the critical elements of the certification process is the idea of the creator contribution.  Hardware often involves many third party components outside of the control of the designer.  Therefore, it is unreasonable to require every component of a piece of hardware to be fully open before becoming certified.

The creator contribution rule is an attempt to address this issue. In order to certify a piece of hardware, the creator must fully open any elements of the hardware that is within their control.  If they have the legal ability to license it, it must be licensed openly.  If they created documentation, that documentation must be freely distributed.

If components were created by third parties, the creator does not have the ability to license them or distribute the documentation.  In those cases, the creator merely has to disclose the parts in the bill of materials and certify that they are available without an NDA.  This system allow creators to distribute legitimately open source hardware without creating a (currently) unrealistic burden to find fully open components.

Assistance

OSHWA has designed this process to be as user friendly and straightforward as possible.  However, it does require users of the certification to make a legally binding promise that they will only use the certification logo on hardware that complies with the community definition.  We recognize that this sort of legal promise can raise concerns or cause uncertainty for some community members.  Therefore, we encourage users to write in to certification@oshwa.org with questions.

While OSHWA will work hard to answer as many questions as possible, some questions may require legal advice.  That is why we have partnered with the Cardozo Law School Tech Startup Clinic.  The clinic has agreed to receive referrals from OSHWA for free and low-cost legal advice regarding the certification process.  We hope to add additional clinics and resources to this program in the future.  (If you are a lawyer who would like to be involved with the referral program, please contact us at certification@oshwa.org).

About Those Unique IDs

Ever since we started discussing unique IDs that were sequential, we’ve gotten variations of a single question: “how can I get a low number?”  In order to give as many community members as possible the opportunity to obtain a coveted low unique ID number, we have decided not to start issuing numbers until the end of October.  All hardware registered before the end of October will be combined into a single pool, from which we will issue IDs starting November 1.  That means that all pieces of hardware registered before the end of the month have an equal opportunity at low registration numbers.  Starting November 1, we will start issuing IDs as hardware is registered.

Version 1

This is the first version of the OSHWA Open Source Hardware Certification program.  It was designed with a great deal of community input and is intended to complement existing pillars of the community.  We hope that you take a look, try it out, and find it useful.  At the same time, we know that as the certification program grows we will find things that can be improved and applications that we failed to anticipate.  That’s why we welcome your thoughts and ideas in the comments of this post, in the forums, in the certification@oshwa.org inbox, and online @OSHWassociation.

In order to provide that feedback, you first need to check out the certification. So stop reading this blog post, click on over to certificate.oshwa.org, and register something!

Don’t have anything documented enough to register?  Bring a project to one of theDocumentation Days around the world (or host your own) as part of Open Hardware Month so you can make it easier for people to build on your stuff.

News broke today that there was a decision in the case that Defense Distributed is bringing against the State Department related to putting files for 3D printing and CNC milling guns online.  While this is a decision on a preliminary question that largely punts on the super-interesting parts of this case, it still has a few noteworthy elements.

As a quick bit of background, Defense Distributed released some files for 3D printed guns online. The State Department sent them a letter telling Defense Distributed that under the State Department’s interpretation of export laws known as ITAR, Defense Distributed had to pre-clear the posting of such files with State. The theory is that posting the files on the internet is the same as exporting them to foreign nationals.

While complying with State’s request, Defense Distributed sued the State Department over their interpretation of ITAR, claiming that the interpretation was unconstitutional.  Before getting to the real heart of the case, Defense Distributed asked the court to suspend the State Department’s pre-clearance requirement until the matter was resolved.  It is that request – which took the form of a preliminary injunction request – that resulted in the decision this week.  That means that the decision today is not about the larger questions surrounding files as free speech, what qualifies as “exporting” a digital thing, and when information becomes a thing.

The arguments around the preliminary injunction can be summarized quickly.  Defense Distributed said that imposing a prior restraint on its ability to speak (in the form of releasing files) infringed on its First Amendment rights (among other things).  The State Department said that releasing files online harmed national security.

The majority opinion essentially took the claims of both sides at face value.  Defense Distributed had Constitutional rights that could only be infringed upon in important circumstances.  The State Department was showing a circumstance which, if it prevailed at trial, could very well be important enough to justify infringing on those rights.

The majority was swayed because of what it saw as the long term impact of those harms.  If Defense Distributed turned out to be right, the harm caused by preventing it from posting the files online could be remedied at the end of the trial (and its appeals….) by allowing them to post the files online (note: it is probably safe to say that this is not a universally accepted theory of how to remedy the harms related to prior restraint).

However, if the State Department turned out to be right, the harm caused by temporarily allowing Defense Distributed to post the files online could not be reversed.  This is because once a file is online it is online forever, even if Defense Distributed took them off the Defense Distributed site.  On this narrow point, this is a refreshingly clear-eyed understanding of how the internet works from a court.

As a result of this balancing, the majority sided with the State Department and declined to allow Defense Distributed to post the files pending the resolution of the case.

The dissenting opinion took a very different view. I suspect that, while Defense Distributed would have preferred to win this round, they are at least happy with the fairly long and detailed dissent opinion.

Instead of taking the State Department’s claim that posting the files online negatively impacts national security at face value, Judge Jones’ dissenting opinion interrogates the claim and finds it sorely lacking.  It questions the constitutionality of the ITAR framework generally, and rejects the way that the State Department interprets it in this case specifically. After undermining the State Department’s argument over the course of a number of pages, it is unsurprising that the opinion sides with Defense Distributed’s constitutional claims and argues in favor of its ability to post the files online.

This opinion may very well be appealed. If it is, the full 5^th Circuit will have to decide which analytic approach to take, and then how that approach applies. Even when that process is over, the parties will have to go back and actually argue the heart of the case (which, regardless of your opinions about gun control, 3D printing, free speech, and export control law, raises some interesting questions).  In other words, this decision is one among many before all of the questions are answered.

That being said, the opinion is an interesting window into how courts will approach the many potentially complicated legal questions connected to this case.  Since Defense Distributed has partnered with the Second Amendment Foundation to pursue this case, there is actually a reasonably good chance that that the case will last long enough to get some of them answered.