Categories
Uncategorized

Makerspaces and Science Centers

Learning

I attended a session at ASTC 2015 titled Are Maker Spaces Killing the Traditional Science Center? Is That a Bad Thing? and while I’m new to the museum world, I’m not new to the makerspace world, but this whole idea of “makerspace in another space” is what the session was about. This post is really just going to be a stream of my own thoughts after the session.

Hooley McLaughlin from the Ontario Science Centre was the moderator and he was anti-makerspace in the context of a science center, where (he believes) the real spark of science can be ignited in young minds. I don’t know much about science centers or the people who work there, but Hooley seems to place “science” (or perhaps just the teaching of science) in this ivory tower, and separate “Science” from other forms of exploration and discovery. The things than happen in a “tinkering” space or a “maker” space are not real science, and there isn’t true learning.

I’ve been involved with Milwaukee Makerspace for nearly five years, and before that I was part of Bucketworks, which is/was a quasi-hackerspace, and I’ve had this idea that BAMspace at Betty Brinn Children’s Museum) Makerspaces tend to be open 24 hours a day, 7 days a week, with everything available to members at any time. 6am on Sunday morning? 3pm on a weekday? Saturday night from 10pm to 4am? Those are all valid times to be at a makerspace working on things. Spaces in an institution are typically limited by staffing, just having people available to be in charge of things. And people like to go home and sleep every now and then, and not work 24 hours a day… also, when people do work, they like to get paid. So the first big disconnect is “makerspace open all the time to members who are self-serving” versus “makerspace that is available during only specific times with staff to guide things.” I’m not saying the second option can’t work, it can, but for people who know what a makerspace is as it exists outside of an institution, reconciling how they operate inside an institution may difficult.

Perhaps it’s just a matter of managing expectations. If the first exposure to a makerspace is within an institution, that can set the stage for what one is, and how it works. (There’s the issue of the term “makerspace” being co-opted or misunderstood, but I won’t get into that now.) Limited access due to hours, staffing, etc. can definitely affect the reach of a space/program, but as most of the institutional makerspaces seem to focus on kids (or families) maybe it’s a non-issue.

Ultimately, my favorite comment during the session pretty much summed things up. “We shouldn’t care how kids get interested in science, as long as they get interested.” My own take on that is, I try things, and make things, and fail, and learn, and in the end, I share those things. I share them with others, and if they get inspired, even just a small bit, than it’s a success. If someone gets interested in robotics, or looks up what an Arduino is, or asks a question about 3D printers, then that’s good enough for me. It’s a spark, and a spark is the start of something. It may not be the spark that (certain) people at science centers are hoping for, but it’s a success in my book.

Categories
Uncategorized

Apple Watch

Apple Watch

I presented a video piece at Maker Faire Milwaukee I called “Apple Watch” which consisted of a Raspberry Pi Model B connected to an Apple Monochrome Monitor from 1988.

The power of component video was harnessed to make a 2012 computer talk to a display that is 27 years old. (Also, Apple used to make solid hardware that lasted a long time!)

The video that plays (after the Raspberry Pi boots up Linux) is the old black & white wristwatch from early versions of the Apple Operating System. The video loops forever and just shows the cursor with the watch hands spinning around infinitely.

You can wait for something else to happen, but it won’t. You can imagine this would fit on your wrist, but it won’t. If the power goes out and comes back on, the Apple Watch will just start up and attempt to run (forever) again. That’s all it does. Really.

Wiring

Raspberry Pi

1988

Apple Watch

Categories
Uncategorized

ASTC 2015 Conference

ASTC 2015

I’ll be attending the 2015 ASTC (Association of Science-Technology Centers) Conference, and learning a lot more about how museums work, at least how they work in relation to technology, which is good, since I’ve been involved in the technology at Betty Brinn for the past six months.

It’s been quite a while since I’ve traveled for any work-related conferences, and the fact that it’s in Montreal, Canada is extra-exciting! I’m hoping that besides all the conference things I may also get a chance to stop by Helios Makerspace and Foulab. (I’m always looking to add to the list of spaces I’ve visited.)

I’ll also attempt to find out more about the Museduino project, which is an open source Arduino-based development kit for museum exhibits. I traded a few emails with Miriam about it last year.

(And since I’ll be traveling with some electronics it’s worth mentioning a conversation I had with others a while back on the subject.)

Categories
Uncategorized

Mouse Control in Processing

Auto

In a recent post I mentioned a silly Processing sketch, and how Vishal and I made the mouse pointer jump around the screen using a Teensy as a USBHID device. This worked fine, but I mainly did it due to lack of time…

The correct way to make the mouse pointer jump around the screen in Processing is below.


import java.awt.*;
import java.awt.event.*;

Robot robot;

void setup() {
  try {
    robot = new Robot();
  }
  catch (AWTException e) {
    println("Robot class not supported by your system!");
    exit();
  }
  fullScreen();
  background(255);
}

void draw() {
  robot.mouseMove(int(random(1,displayWidth)), int(random(1,displayHeight)));
  delay(100);
}

This code does not work in ProcessingJS, but if you’re running Processing sketches in the IDE or as a standalone application, it works great.

Categories
Uncategorized

The Detonator

The Detonator

It’s The Detonator! What is The Detonator you ask? Well, for Maker Faire Milwaukee we build a fire poofer, which is a device that shoots flames into the air. Workmate John McGeen started the poofer build and we finished it up at Milwaukee Makerpace. Along the way we experimented with a torch, candles, and grill igniters, until Dan the Blacksmith finally added a pilot line and some steel wool.

Fire Poofer

The Detonator went through a few revisions, but I’ll walk through the construction of it for this blog post. We brainstormed a few different ideas to trigger the poofer, but in the end I went with something simple than I knew would work reliably for the entire weekend. (And it did!)

Laser Cut Parts

I started by using MakerCase to design a box I could laser cut. I used 3mm black acrylic because I have a lot of it, and I made the box the size that worked with the acrylic I had. The image shows the acrylic (gray parts) and one piece of 1/4″ wood (which is tan in the image.) The wood piece went on the inside, right under the top acrylic with the hole for the button.

The Detonator Guts

Since I wanted The Detonator to withstand being pressed, slammed, and pounded on by hundreds of people over the course of two days, I also built a wooden box that fit inside the acrylic box. This added strength and weight to it.

Vinyl

I didn’t just want a plain black box, so I added some bright yellow vinyl to it. I cut the vinyl with a Silhouette Cameo. The image above shows how I determined wrapping the vinyl around the edges.

The Detonator - Vinyl

Here are the vinyl pieces I cut. I added cut outlines around the pieces so I’d be able to line it up correctly. It worked pretty well. (I didn’t take time to measure or mark things, but that would be a recommendation.)

The Detonator - Illustration

Above is my final “pretty” illustration of The Detonator. Below is a very black photo of The Detonator. I’m fairly pleased with how it turned out, especially since it was a rush job to build it.

The Detonator

The Detonator Connectors

There are four connector posts, but only two got used in the end. I originally had just the two in the center, but ended up splitting them and adding extra posts so I could split power between 12 volts (well, 18 volts, sort of) for the solenoid, and 4.5 volts for the grill igniters. We ended up ditching the grill igniters, so in the end I only needed one pair of connectors. Oh well!

The Detonator Guts

Here’s the inside! There’s a Pololu A-Star 32U4 Micro mounted on an Adafruit Perma-Proto Half-sized Breadboard PCB with some screw terminal connectors, which is connected to a relay board. The board I used had four relays, but since we didn’t use the grill igniters I could have used a two relay board. (Also, relay boards are super-cheap on ebay.) There’s also a relay controlling a beeper that beeps a countdown. (See the video below.)

Overall The Detonator was a quick build. and there’s a few things that could have been a bit more polished. For instance, I cracked the acrylic a bit when I drilled more holes for the connection posts. In an ideal world I would have laser cut a new piece, but I didn’t have time. I also could have made the code a bit simpler after removal of the batteries for the grill igniters, but hey… The Detonator turned out good for a quick fire poofer controller!