While capturing the time-lapse last week, John and I ran into two irritating issues. The first is that the moving platform causes the object being printed to come in and out of the focal plane of the camera and makes for a jarring video. The second is that because the interval between photos is constant, some large and slow layers will have multiple shots taken while several consecutive quick layers can be skipped entirely. The solution to both of these is to dynamically remote trigger the camera from the printer.
I wrote a Skeinforge photograph plugin that inserts a new G-code command, M240, which tells the printer to trigger a photograph. The module offers three modes. End of Layer, as demonstrated by Yoda above, is the simplest. It takes one picture at the start of the first layer and then another at the end of each layer of the print, resolving only the second of the aforementioned issues. Corner of Layer takes a picture at the minimum Y,X of each layer. Least Change between Layers tries to take shots that are as close as possible to each other from layer to layer. I had the most visually interesting results with the last setting, as shown in the Flower print up top. The module can be downloaded from github, and installation instructions are included within its text.
The other half of the control scheme is triggering the camera from the RepRap. Since I didn’t want to risk coupling my T2i directly to the printer, I went for emulating a Canon RC-1 Remote, which has been thoroughly reverse engineered. The hardware is simply an 850nm infrared LED in series with a 180 ohm resistor connected to one of the I/O pins on the Arduino Mega. I chose pin 23 because I could solder to it without pulling my RAMPS board off. The software side is equally simple. For this, I forked the excellent Sprinter firmware to respond to M240 and send the correct pulse over the IR LED. My fork is on github, but the diff that adds M240 support is the interesting bit.
John visited recently and suggested that we bring another photographic production to the world: this time, a time-lapse of the RepRap printing out an interesting looking object. After some frustrating attempts to install the Canon EOS Utility, we just used an intervalometer directly on my T2i with the Magic Lantern firmware. In case you want to try it out and to save me a lot of Googling in the future, here are the mencoder parameters to generate a sanely sized video from high resolution stills.
mencoder -ovc lavc -lavcopts vcodec=mjpeg -mf fps=10:type=jpg -vf scale=960:720 'mf://*.JPG' -o timelapse.avi
Depending on which project gets swapped into my next free time slot, I may have another post soon exploring an extension on this that John and I discussed.
Now that I’ve recovered from Maker Faire, I can continue documenting what I did. In the lead up to the event, I tried to streamline the FaceCube project as much as possible so visitors wouldn’t have to waste precious Faire time waiting for a print to start. On the hardware side, I kept the extruder and heated bed warmed up to operating temperature and (literally) hot swapped 4″x4″ pieces of glass so that prints could run back to back. I updated the FaceCube script to do capture, cleaning, meshing, scaling, and running through OpenSCAD with a single button press. The remaining bottleneck was running Skeinforge on my geriatric in computer years laptop. Skeinforge is an amazing utility, but written in Python, it is slower than a drunk sloth.
There are ways of speeding up drunk sloths though. Psyco is commonly recommended, but does not support 64 bit architectures. My roommate Will came up with a plan to run a Skeinforge server on PyPy on a faster computer and have a client on my laptop send STLs to it for skeining. We ran out of time on that, but we did get PyPy running normal Skeinforge on my laptop. As of PyPy 1.5, there is support for Tkinter. Following those instructions to install PyPy and Tkinter and run Skeinforge on 64 bit Linux:
wget https://bitbucket.org/pypy/pypy/downloads/pypy-1.5-linux64.tar.bz2 tar -xjvf pypy-1.5-linux64.tar.bz2 cd pypy-c-jit-43780-b590cf6de419-linux64 wget http://peak.telecommunity.com/dist/ez_setup.py ./bin/pypy ez_setup.py ./bin/easy_install tkinter-pypy ./bin/pypy ~/path_to_skeinforge/skeinforge.py
The fonts may look slightly different, but the application should behave the same. Export times should decrease the first couple of times you put a file through as the JIT compiler optimizes and then stay good as long as you keep the process running. On my laptop with a 2.00 GHz Core 2 Duo, Skeinforge runs 2 to 3 times faster on PyPy than on stock CPython 2.6.6. The tested objects were a Weighted Storage Cube, a Flower, Whistle v2, and the Prusa Mendel vertex.
To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries.
Article I, Section 8, Clause 8, United States Constitution
One of the few Congressional powers specifically enumerated in the Constitution over two hundred years ago allows for the protection of intellectual property rights for a limited period of time. Limited is, like much of the Constitution, intentionally vague. In theory, depending on the whims of the judiciary in place, limited could be defined as anything up to the heat death of the universe. Recent judgments put this within the realm of possibility. I will not use this space as a discussion (rant) about copyright law or reform, mostly because there are much better and more interesting places to read about that. I will, however, describe my experiences as a user of copyright and propose a workaround for some of its woes.
The Copyright Act of 1976, as confirmed in Kahle v. Gonzales, changed copyright from an opt-in system requiring registration to an opt-out system, in which any copyrightable work is automatically copyrighted upon publishing. That means that without any intervention on my part, under current copyright law and assuming no further extensions, this blog post will enter the public domain April 25th, 2080 if I croak immediately after hitting the Publish button. As my red meat intake has been limited recently and Congress is still in the pocket of big business, I expect the actual date will be much later.
Many rightly find this unreasonable, hence the rise of the copyleft and free culture movements. Practically perpetual copyright isn’t so bad when the work is opened by a permissive license like Creative Commons Attribution or three clause BSD or a reciprocal license like the GPL. Or is it? If in 2134, a brain hacking hobbyist decides she wants to repurpose and distribute a Python game I wrote in 2009 as a retro eyesaver, should she really have to include the ISC license stating that my corpse disclaims all warranties including implied warranties of merchantability and fitness? I argue that in a sane society, she should not, as the work would long have been in the public domain. However, the license I attached to the work will remain valid for the entire absurd length of its copyright.
I propose a simple workaround for this problem: a self-destruct wrapper for licenses. That is, a legal instrument by which the owner of a work can specify that he or she voluntarily and automatically relinquishes the work into the public domain after a specific number of years. This is à la carte copyright, in which the creator may choose a length that seems sane, like the 14 years we started with in 1790. This also has the effect of trumping any further extensions Congress may enact to keep Steamboat Willie in the vault, preventing a work I publish today from remaining under copyright in 3010. One could use such a wrapper on any license, permissive, reciprocal, or restrictive. An individual or company could profit from a work for a period of time of their choosing, and automatically grant it to the betterment of society at the self destruct date of the license. A software developer can protect a piece of code from going proprietary with the GPL today without forever limiting projects that use it to a copyleft license. I could protect myself from exploitation by marking a photograph I’ve taken as CC by-nc-nd for now without preventing its public use long after my death.
I can’t even pretend to be a lawyer, but here’s a proof of concept ripped from a piece of the Creative Commons Zero license.
/* Upon the date of publication, the License shall be deemed effective. Upon X years from the date of publication, the Waiver shall be deemed effective. Waiver: To the greatest extent permitted by, but not in contravention of, applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and unconditionally waives, abandons, and surrenders all of Affirmer's Copyright and Related Rights and associated claims and causes of action, whether now known or unknown (including existing as well as future claims and causes of action), in the Work (i) in all territories worldwide, (ii) for the maximum duration provided by applicable law or treaty (including future time extensions), (iii) in any current or future medium and for any number of copies, and (iv) for any purpose whatsoever, including without limitation commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each member of the public at large and to the detriment of Affirmer's heirs and successors, fully intending that such Waiver shall not be subject to revocation, rescission, cancellation, termination, or any other legal or equitable action to disrupt the quiet enjoyment of the Work by the public as contemplated by Affirmer's express Statement of Purpose. License: ... */
Since I am not a lawyer, I have no idea if a self-destructing license is legally possible. I would like to get lawyerly advice on the idea before I start attaching it to my projects, but this is certainly something I plan on using. Hopefully it appeals to others too. Since the bug fix for perpetual copyright isn’t coming any time soon, this workaround will have to do.
At some point in high school, my friends and I decided to learn the lost craft of home distillation. We started with the best of intentions (well, not really), but were unable to build stills that functioned until we hit college. Since then, we have just about perfected the process of distilling tasty, cheap rum on a stove top. John Martin has chronicled our steps and missteps over the years in a series of blog posts. The first three cover the background story, the basics of fermenting a rum wash, and the general process of distillation. The final post covers the specifics of urban moonshining; that is, plans for a micro still that allows for home distilling within the confines of the average apartment.
Another rumbling done.
A brilliant idea by Meg Blake.