It Lives, Again?

Well, I have completed the classroom component of my time in Fleming College’s Museum Management and Curatorship Program.  I know that I didn’t post about my time in the program on the blog, but I wasn’t silent- I chronicled what I was doing on my portfolio, which is now part of this blog! Check it out sometime.

I can say with more conviction that there will be some posts coming up in the next few weeks. I know that this is not the first time I’ve said that and then disappeared for most of a year, but this time the blogs are for an assignment, so, rest assured, you’ll see them.

The third (and final) semester of the Museum Management Program is an internship with a museum or cultural institution. I am currently interning at the Bell Homestead National Historic Site. Throughout the next four months I will be posting “Internship Journal” entries chronicling my experiences at this National Historic Site.

I am also thinking of using this blog as a platform for some of my personal research (which is what blogs are for, after all). You may be seeing some preliminary stuff for that as well.

In any case, I will be writing here again soon! (and I mean it this time!)

Scott W. E. Dickinson



It Lives

Life, do you hear me? Give this blog life!

Well, it’s been awhile.

More than a year, really.

I am proud to say that I’m getting back into the Public History gig- as a student at Fleming College’s Museum Management and Curatorship program. It’s not exactly where I expected to be when I last wrote in this blog, but it is a spot in the heritage field where I can improve my skills and make further contacts in the museum world. If it only paid me, it would be perfect.

On that note, I will likely  have something to impart about my year-long job search (don’t worry- I wasn’t unemployed for a whole year, but I wasn’t in a museum or heritage related institution), though I’m not sure what I can tell others about finding employment, considering that I didn’t.

Expect more from me (fairly) soon about new projects, new exhibits and new ideas

I swear I’ll get a job Ma,

Scott W. E. Dickinson

Now What?

Another four months, another change.

That sounds really familiar for some reason, doesn’t it?

Though I had planned to occasionally rite about my summer term experiences at Fanshawe Pioneer Village, it looks like all I can do now is an end-of-summer retrospective.

Turns out that being an archive assistant is very busy work! My internship at the Pioneer Village was a great experience that gave me a chance to work with many aspects of museums. Not only did I work with the Village’s archives, but also with their collections, their exhibition space and with the interpretive staff. I spent most of my time working in the Village’s archives, but certainly not all of it.

The largest project I was involved with was the relocation project I mentioned last time, though ‘moving a few collections’ is certainly underselling what we did. Moving, conserving, accessioning and storing several thousands artifacts is no mean feat. The sheer number and variety of artifacts that were moved was downright astonishing. Everything from sleighs to stoves to safes and clocks to chairs to cookware were in evidence.

The projects that I spent the most time on, however, were based in the Village archives. Although originally I was only going to complete one archival project, this soon blossomed into a much larger undertaking. In the end, I created and organized eight new collections, wrote Finding Aids for them (Finding Aids are archival directories- they tell you how collections are organized and how to find documents within them) and relocated them to new places in the archives storage area. These eight collections totalled more than twelve hundred documents and represented several weeks of steady and rewarding work.

I also interpreted historic buildings- while in costume!- helped design and implement an exhibit, cleaned and conserved a great many unique objects and got to work with an amazing collection of historic artifacts and objects.

In all, the summer term was a great sucess. Not only did I gain a deal of useful experience, but I helped out a local institution in a very real way.

Yet Another Chapter

Another four months, another change…

Well, Summer Term is upon us, and for once I have something school related to do.

Though since I’ll be receiving my Master’s Degree by the fall, this could very well be the last university related thing I ever do.

We’ll have to see.

Anyway, in a few short hours I will be starting my summer internship (the final requirement for my Public History degree before I can graduate) at Fanshawe Pioneer Village, located in the city of London, Ontario. Fanshawe Pioneer Village recreates the early life of settlers in Middlesex County, and was set up in the late 1950s, making it a rather early historic village for Canada.

I’ll be working to help preserve and catalogue several collections that have been stored in perhaps not optimal conditions, while also working with the public and on an organizational project within the Village’s archives.

I’ll have more on all of that later, so stay tuned!

One of the Village People,

Scott W.E. Dickinson

Wrapping Up WALL-E II

Well, that’s it for the ol’ robot.

We had a little presentation last week of all the projects our class had been working on. They certainly seemed impressed by WALL-E and I’s little back and forth. More on that further down.

I promised in my last post a more in-depth discussion of how I programmed my WALL-E animatronic, and here it is.
Now that the program (or ‘patch’, as Max 7 likes to call them) is fully completed, I can finally show it and explain how it all works.


Here you can see just how large this patch has grown. All this is required for a show lasting about a minute- and that’s with me providing most of the dialogue! WALL-E II mostly reacts to what I say- or, rather, I time my questions so that his movements appear to correspond to what I ask. Voice recognition was, I felt, perhaps a little too ambitious for this project. Since the patch is so large, I will break it down into four sub-sections, to make the explanation a little easier.

servo 1

This is the first section of the patch. Here you can see how the entire program is activated, and the first set of WALL-E’s movements. No.1. is a keyboard input, which allows Max to register which keys are being pressed on my computer. The Indicator connected to it shows which key Max is currently detecting. Each key on the keyboard is assigned a number (even the letters. confusing, no?) and the four numbers on No.2 (28, 29, 30, 31) represent the four arrow keys, specifically left, right, up and down, in that order. As you can see, four connecting lines leave the route function and move further down into the patch. Each one is connected to one of WALL-E’s four sets of movement commands. The route function allows the input from the key function to be sorted based on what that input is. As you can see, when the left arrow key (which has 28 as its corresponding number) is depressed, route sends that signal to the button that you can see on screen at No.3.

The button is one of two switches that I experimented with. The button, like its real world namesake, stays active for only as long as someone is acting upon it while the toggle (not shown here) is like a switch- it stays flipped even after you walk away. Since I only needed to ‘jump-start’ each sequence of actions, I used a button.

No.3 is a counter function. This particular counter has been set to count to seven. It will count to seven (0,1,2,3,4,5,6,7), looping back to zero after seven is reached. When controlled by a button, the counter counts forward once for each ‘press’. With a toggle, it would continue to count forward without ending until the toggle was switched off. Since I wanted to have to use the keyboard as little as possible (so as to sustain the illusion that I was not directly controlling WALL-E), I preferred the button. If you look at No.4, the line function has two sets of connectors coming from its outputs. One set travels down to the bottom of the patch, where it connects to what actually outputs the control signals to the servo control board on WALL-E himself. The other set of connections returns to the counter function above. This allows the patch to send each set of instructions automatically, without requiring an operator to press a key after each movement.

It works like this. Normally, the counter is resting on seven. With no inputs from anywhere, this is a neutral state. Once the operator presses the corresponding key, the counter resets to zero. You will have noticed the route function connected to this counter. When the counter resets to zero, it sends a signal to the button connected to hit. When this button is hit, it momentarily activates the ‘message’ attached to it. Each of these messages (the rounded gray rectangles with numbers in them) is one of the servo commands. The first two numbers represent the start and end positions for the servo and the third is the amount of time this movement will take in milliseconds. For reference, 1000 milliseconds is 1 second. This command is then passed through the line function, which helps smooth out the movement of the servos and down to the servo output functions. A command passing through the line function sends a signal through the connectors leading back to the counter, causing it to jump to the next number, which is 1. This, of course, triggers the commands connected to 1. The counter can no longer rest on any number besides seven (which does not have any actions connected to it) since any other number will trigger the counter to move forward until it hits seven, which is now its rest state.

There are two line functions because they each control a different servo. One controls the vertical movement of WALLE’s eyes, the other the horizontal movement of his head.

Servo 2

Here’s the second part of the patch. No.1,2 and 4 are very much the same as the last one. This button corresponds to the right arrow key and the counter goes to 10 since this is a slightly longer sequence. No. 3 is the big change here, since this is a new action, unrelated to the servo movements. It is actually very straightforward. It consists of an mp3 sound file, an audio output function and a toggle (a button doesn’t work here- I need the file to play all the way through) connected to the route function. When the counter reaches the right number, it activates the sound, which plays through my computer’s speakers. You may notice that there is more than one connector coming from the same route output. This is so that WALL-E can move his head in time with the sound file, so to make it look like he is speaking to his audience. Also note that not all the messages have the same duration time. If I want WALL-E to perform an action quickly or slowly, I must alter the timing until the movement emulates the feeling I want him to convey. Also, one can connect multiple lines from several route outputs to the same button so that WALL-E performs the same action several times. I found this very useful when I wanted him to shake or nod his head.

servo 3

The third part is not very interesting. Note the gaps in the route function output. I found, while programming, that when I have both servos performing actions simultaneously each line function sends a signal back to the counter, moving it ahead two spots instead of one. When I tested this section, I found that the counter would automatically roll over as too many signals came in, putting it in a permanent loop. I solved this by making the counter go to a higher number (it was originally seven) and spacing out the lines on the route function. Now it goes only to ten and stays there until I reset it manually. At the bottom of this section there is yet another set of line functions, which will join all the rest at the bottom of the patch.

servo 4

Here’s the bottom of the patch. It’s a been a bit of a ride, hasn’t it? Here we see the last set of line functions (No.1). They, along with the other six we’ve seen, connect to that set of indicators that tell the operator what the positions of the servos are (No.2). From there the signals travel to the output functions, which were pulled directly from the servomotor patch that comes with every copy of Max 7 (No. 3 & 4).

Four sets of line functions may seem a bit redundant, but they were necessary. First, this patch grew so large that rather than try to scroll through it to connect all together in one place, I created several pairs of line functions to act as local ‘outlets’ that went directly to the servo outputs. That way, I didn’t have to thread all my lines down to the bottom of the page. Given the number of commands, this would have been messy, hard to inspect and impossible to troubleshoot. As well, each counter required a separate input. If all four counters wee attached to the same line four would have activated at once, sending the servos a confusing array of conflicting commands.

I’m reasonable happy with how WALL-E turned out. For my first attempt at something like this, I feel that he was a success and that his movements added something to the little ‘talk’ I had with him. If I ever rebuild him, or make another animatronic, there are a few things on my wish-list. The first is a great range of motion. I was very pleased with how expressive the movement of his eyes was, but I found that WALL-E could only really turn his read to the left, not to the right. In the future, bigger servos, or ones with great ranges of motion would be preferred. I also wish that I had time to design a few more servos into WALL-E. My original plan from January included an arm that WALL-E could wave up and down. Thanks to time constraints, I decided to leave the arm (which I had made) off the final body. As well, I would have liked to put a motor controlling some eyebrows (for added expressiveness) on WALL-E’s head, but the motor for his eye movements bent his head frame badly by itself and I did not feel it could stand another motor. A longer show, of course, goes without saying, but since this was meant to be a demo, I feel a minute of showtime was adequate. I had also hoped to install a few LEDs in WALL-E, to flash on and off with his speech. This was to make it more clear to the audience who was ‘speaking’ when the audio files played. In the end, that turned out to be unnecessary- WALL-E bobbing his head was an obvious enough effect. To sum up, WALL-E II was a good demo and testbed, and as a first try I feel he was very successful. If I ever try to make another animatronic, a sturdier frame, a few more servos and more time to play around would be very nice!

Why Use Animatronics in History?
In closing, I’d just like to point out a few words about how something like WALL-E II could be useful in an exhibit. My presentation consisted of myself asking WALL-E questions, his answers and my responses to those answers. What made it work, despite WALL-E having only two lines, was that we made it interesting. WALL-E ignored me, had to be woken up, refused to say his name (at first) and looked away from me while I tried to speak with him. The net result was that it seemed my own creation was not interested in listening to me at all. This is maybe a rather strange version of interactivity- the animatronic is not really responding to what I say, but it certainly looks like I am to the audience. Though I was the middleman between WALL-E and his audience, the show was nevertheless for them, and involved actors who were decidedly non-human. This, as I’ve argued before in this blog, is the usefulness of the animatronic in designing exhibits. The animatronic can be a rare bird, a wise old tree, a replicate of an artefact that comes to life before one’s very eyes (imagine being able to listen to a totem pole tell it’s own story). It may only be the illusion of life, but we can make it seem pretty real.


Keepin’ it Unreal,
Scott W.E. Dickinson

(P.S.- this blog will be undergoing yet another change as Summer term starts- tune in near the beginning of May to find out why!)

Gilderfluke and Max 7

It Lives!

Unfortunately, WordPress won’t allow me to upload the short video I’ve taken of my animatronic, but I’ve entered the final stage of creation for my project: Finishing the program for it’s little show.

One of my classmates has noted my animatronic’s resemblance to a low-budget version of WALL-E, the robotic star of PIXAR’s movie of the same name. WALL-E is a character of few words, which is perfect, since my animatronic will only be capable of saying a few words! Or, rather, I only have time to program him to say a few. So, my previously unnamed animatronic will be christened, however belatedly, as WALL-E II.

I found, when fiddling around with Max (more on that below) some interesting ways to get my program to unfold. At first, each new movement of my animatronic was controlled by a small clock (or metronome, as Max calls it), each step in the program following the last at a set interval. This was not exactly ideal. Since each new action was triggered at the same interval as the last, no action could last longer than what the metronome was set at. Actions that took less time would cause the animatronic to move, then pause noticeably before the next set of instructions were delivered to the servos. Since I needed my animatronic to pause and move at different rates, this would not work.

A different solution presented itself. I needed each action to follow the last right after the previous had ended. Was there a way to do this? Luckily, yes. By removing the metronome and connecting the output of the servo instructions back to the counter (which was what moved between steps in the instructions), the end of each action would trigger the next one in the series. This was far more satisfactory. Now, I could have an action that lasted several sections, followed by several which lasted only fractions of a second. In short, my animatronic is now capable of far more nuance and expression than he was before.

A few weeks ago I had felt I had reached a roadblock with programming. It was very easy to control a single servo directly, and giving it instructions via Max was not difficult at all. My main problem was in commanding more than one servo at a time, which I found difficult to do. Max seemed to only want to control one servo at a time. It turns out that there was a simple fix available, and my professor would supply it to me, but in the meantime I thought it necessary to look at some other software that might do what Max wasn’t.

Hence Gilderfluke. Gilderfluke and Company is a firm that designs and manufactures entertainment electronics, including animatronic controls and components. They do a lot of work of Disney, Universal Studios and all the other big names in animatronic entertainment. And almost all of their stuff is far out of my price range. Except for a bit of free software that Gilderfluke offers to hobbyists. I downloaded this free software and found that it was far too detailed for my little project. Although a comprehensive program, Gilderfluke PCMACS (the name of the program) was not exactly beginner-friendly. It took me the better part of an hour to find what I think is the programming tool. It is immensely detailed, and with it one could program an entire show’s worth of animatronic characters.

It’s also much less intuitive than Max 7, and rather less user-friendly (PCMACS was originally designed in 1999, and it shows). At the point when I realized that PCMACS would be almost unuseable in the time frame I had to learn it, my problem with Max was solved. Good thing Gilderfluke just gives this program away.

If this explanation was unclear, don’t worry. My animatronic will be complete next week and soon after I put a complete after action report about it, including an illustrated guide to the patches in Max that I used (as well as some developmental ideas, and stuff I would’ve like to implement if I’d had another month or two).

WALL-E’s talkin, but I wouldn’t expect walkin’.
Scott W.E. Dickinson

A Progress Report

We’ve got a robot, folks.

Or, at least the beginnings of one.


Not exactly the greatest face out there, but once I get the LEDs in there it’ll be (hopefully) a bit more expressive.



As you can see, he uses servos to move (check in again soon for a post where I demonstrate the current range of motion). One servo controls the head’s left and right movement, while the other nods the eye assembly up and down. I’m hoping to add some more movements soon. The Phidget servomotor control board that interfaces with my computer is located inside the body itself.


Here’s a shot of the full figure as it is now. I hope to cover some the k’nex body work with some decorative cardboard to make it look more like you average movie robot, non-functional control panels and all.

Check Back Soon for some Movement!
Scott W. E. Dickinson