It’s the height of summer in the Northern Hemisphere, and hackers and makers everywhere are letting their hair down and enjoying the hot weather on the water. By coincidence last weekend there were two very different raft races in the European hackspace community, at the SHACamp2017 gathering in the Netherlands the villages competed in a cardboard raft race, while on the other side of the English Channel the various hackspaces in and around London came together in a raft race using more conventional materials.
The SHA race came about through the happy confluence of a surplus of disposable cardboard tents, a sunny afternoon, and the inviting waters of the Nuldemauw. The aim of the contest was for hacker camp villages to make it from the bank to the end of the boat dock, a distance of about 100m, in a boat made from cardboard there and then at the camp. Meanwhile the London spaces met at City Road Basin in London with their more robust watercraft for a series of races, the aim of which seems to have been to be the first to get their crew disembarked at the other end of the course. and sitting in a chair on the bank.
In both races the inventiveness of the entrants showed itself in a wide range of boat designs. As you might expect those craft with a wider beam fared better than the far less stable narrower ones, with capsizes a feature at each location. Clear winners in the Netherlands were a pair of German teenagers in a very stable wide raft, while in London it was South London Makerspace’s catamaran that scooped the crown. There is a video of the London race which we’ve placed below the break.
The hackspace and makerspace spirit is at its strongest when bonds are forged between members of different spaces. Skills and capabilities are shared, collaboration opportunities abound. The sight of a bunch of European makers getting wet might serve more as entertainment than edification, but behind it lies an important facet of hackspace culture. If you’ve not yet been the spaces closest to yours, do so. You never know, one day you might end up on a capsizing raft because of it.
The 2×4 Contest at my local hackerspace captured my interest. The challenge was to build something cool out of a single eight-foot 2×4 with the winner getting free wood storage in the space. I had half an idea for a project, but I ran out of time and never even started it. My idea was to cut the board into half-thickness strips and glue them edge-to-edge with some biscuits holding them together — to basically make wider, thinner boards to do… something cool with it.
One of the entries is pictured above. [Jon Alt] designed this clock and phone charger that includes a capacitive charger for his smart watch. He makes use of the 2×4’s grain to make a gorgeous enclosure, carving away the rear of the front panel so only a credit-card’s thickness of wood remained, allowing the 7-segments to shine through. The other entries were great as well and I especially liked the 2×4 guitar.
Mostly what interested me about the contest was what it showed about the wood shop: thanks to the volunteers and board, that is a wood shop doing well. Stuff is going on! A sad wood shop doesn’t hold contests. By extension, when the shop is doing well, that means the hackerspace is also doing well.
A wood shop is one of those areas of a hackerspace that is tool-driven. It’s not just a gathering place for like-minded folks; people go to use a specific tool or tools they can’t afford, and let’s face it, there’s always tools to buy that costs a bunch of money.
I’ve seen this particular shop begin as an empty concrete room with a cheap drill press and someone’s old bandsaw. Pretty soon worktables, shelving, and storage were built. More tools arrived, some donated, some loaned, some purchased with dues. So how can other spaces replicate this wood shop success story?
There’s something about old industrial buildings that just seems to attract hackerspaces. It could be the open floor plans typical in buildings that used to house big manufacturing operations, or it could be a desire to reinvigorate places where machines once hummed and skilled hands plied their trades. Whatever the attraction, the relationship is not without risk; old buildings with wood floors and frames can be tinderboxes, and tragedy can strike at any moment.
Such a fate befell The Foothills Community Workshop in Granite Falls, North Carolina, this past Friday. Details are still sketchy as the remnants of the 75,000-square foot former Shuford Mills textile factory are still smoldering, and the Fire Marshal’s investigation is not yet complete. Thankfully, no lives were lost, and injuries were limited to heat exhaustion of several of the firefighters from 16 counties who battled the blaze in the hot and humid North Carolina Piedmont.
Last year we wrote about Hackerbot Labs’ autonomous boat, which project members hope to someday circumnavigate the globe. Now called Project Ladon, progress continues apace with a recent ocean test of their modified 18’ kayak, the TSV Disputed Right of Way. The kayak’s internal spaces contain a pair of lead-acid truck batteries controlled by a home-brewed control system that uses relays to control the craft’s trolling motor, with a Beaglebone and Arduino Mega under the hood.
The test was not exactly a success, with the boat actually avoiding the waypoints rather than sticking to them. Fortunately the team was aboard a chase boat so they were able to keep tabs on the craft. Unlike a quadcopter, which just falls down, a watercraft that borks may never be seen again.
When the [Director of Legal Evil] at Louisville’s LVL1 Hackerspace decided to demonstrate the uselessness of a 3D printer by printing a fidget spinner, another member at the space’s Tuesday meeting rose to the challenge and built a machine that whose sole purpose is to spin fidget spinners.
[Gary Flispart] used an Arduino clone and what appears to be a motor driver in conjunction with a stepper motor. The motor moves a belt that turns a series of metal scraps serving as a four-bar linkage. The linkage moves the dowel that turns the spinner and then gets out of the way so it doesn’t inhibit the toy’s rotation. The Digital Fidget Digit, as [Gary] calls it, looks like it was built out of scrap metal and random pieces of wood in the glorious tradition of hackerspace projects.
More than one member of the Hackaday team has significant involvement in a hackspace, as member, director, or even founder. We talk about hackspaces quite rarely on these pages though, not because we don’t have anything to say on the matter but because even when we write in general terms our fellow members invariably think it’s all about them rather than the hackspace world at large.
For once I’m going to break the silence, and not only talk about hackspaces, but talk about my own hackspace in specific terms. Because, fellow Oxford Hackspace members, this isn’t about you personally though I’m using our home to illustrate a point. The topic is a thorny issue that must affect all spaces, that of donations of physical items. People want to help their hackspace, they have a pile of what they consider to be good stuff, and when they’re having a clear-out they make a donation. But, as we all know, “one man’s trash is another man’s treasure” and vice-versa. Continue reading “The Complex Issue Of Hackspace Donations”→
When you are running a hackspace, network security presents a particular problem. All your users will expect a wireless network, but given the people your space will attract, some of them are inevitably going to be curious enough to push at its edges. Simply plugging in a home WiFi router isn’t going to cut it.
At Santa Barbara Hackerspace they use Unifi access points on their wireless network, and their guest network has a system of single-use codes to grant a user 24-hour access. The system has the ability to print a full sheet of codes that can be cut individually, but it’s inconvenient and messy. So the enterprising hackspace members have used a Raspberry Pi and a receipt printer to deliver a single code on-demand at the press of a button.
The hardware is simple enough, just a pull-up and a button to a GPIO on the Pi. Meanwhile the software side of the equation has a component on both client and server. At the server end is a Python script that accesses the Unifi MongoDB database and extracts a single code, while at the client end is another Python script that reacts to a button press by calling the server script and printing the result. It’s a simple arrangement that was put together in an evening, but it’s an effective solution to their one-time WiFi access needs.
It’s a temptation as a hackspace to view all of your problems as solvable in one go with the One Piece Of Software To Rule Them All, and as a result some spaces spend a lot of time trying to hack another space’s effort to fit their needs or even to write their own. But in reality it is the small things like this one that make things work for members, and in a hackspace that’s important.
Does your space have any quick and simple projects that have automated a hackspace process? Let us know in the comments.