Samsung Presenter

When I teach at UWM we’ve got this presentation camera at the front desk that can be used to show the Arduino and a breadboard and how things are connected. I believe it’s a Samsung SDP-860. It was probably awesome in its day, but the quality is not amazing. It does have a number of controls to zoom in and adjust the brightness, and has a built-in light and multiple outputs, but I still am not impressed with the image quality. When I did use it, I just connected it via USB to my MacBook and used QuickTime Player to get a video window and then showed that with the projector. It allowed students to see the tiny components I was using… so yeah, it worked.

But then I thought to myself, “Why not just use a webcam!?” and that’s what I’m going to do. Since I’m not teaching in the Spring semester I offered to do a Beginner Arduino Class at Milwaukee Makerspace, so I built my own camera thing… the Raster Presenter!

Raster Presenter

Yes, it’s basically a desktop microphone stand. There’s a long gooseneck to allow positioning the camera to point directly down at the desk. (It’s similar to the gooseneck rig used on Time Lapse Bot III.) I’m using a Logitech C910, which I’ve had for years, and which outputs some decent quality video.

Raster Presenter

The Raster Presenter is not quite as pretty as the Samsung model, but I dare say the quality is better, and it may even be more adjustable. It’s also lighter, can be disassembled, and does not require an external power supply. (Just a single USB connection!)

Raster Presenter

The camera mounts to a small piece of wood using zip ties that fit into notches. The wood slides into half of a mic holder that came with the mic stand. There’s a little bit of gaff tape to stop it from rotating on the gooseneck, and Bob’s your uncle!


When you launch QuickTime Player you just choose “File” and then “New Movie Recording” and you should see some live video. If it shows the computer’s built-in camera you can change it via the drop down menu.


After choosing the proper camera you can also choose to change the quality. I found that “Maximum” gave much better results than “High”, although it did seem to enable the auto-focus in the camera, which can occasionally be an issue (at least with other webcams I’ve used.)


Once you have all your settings you can move your mouse off the window and the controls (and title bar) should disappear. As long as you’re connected to a projector your students are ready to see the small things you want to show them! In the sample shot above the only light I used was daylight from the window to my left. I could see a bit of static in the image, but even in low-light it looked pretty good. I’ll do some testing to see if I can get away with existing light or need to augment it with another light source.

USB Fail

Checking on the meaning of the word “troubleshoot” shows it to be defined as “trace and correct faults in a mechanical or electronic system” and the word “debug” describes “the process of identifying and removing errors from computer hardware or software”.

I use both of these words, a lot, and I hope I’ve used them enough in class to plant the idea into student’s heads that both of these words are really about problem solving, which is probably the most important thing you can learn in my class. If you’re dealing with physical things or electronic things, they are not always going to work, and figure out why they don’t work, and getting them to work is what it’s all about.

I recently had a student who had written some very simple code. It checked the distance of an object using an ultrasonic sensor, and when the right conditions were met, it turned a servo. This is dead simple, but for a student not well versed in writing code, can be a challenge. The student could not get it to work reliably. It worked for maybe 10 to 30 seconds, then froze up. I ended up wondering if there was a conflict between two code libraries, did some searches, determined there might be, found a way to write code without using a library, had the student test it, and the results were the same. I then duplicated the student’s circuit, ran the exact same code, and it worked fine for me. I then swapped servos with the student, then ultrasonic sensors, then Arduino, then… Then I just took the entire setup from the student, Arduino, USB cable, breadboard, wiring, sensor, servo, and tried it on my computer and it failed. Failed! Did not work. Eventually I discovered the student had a bad USB cable. Yes… a bad USB cable, that “sort of sometimes” worked. Sometimes. It worked reliably enough to upload code, but the student kept getting errors when trying to open the Serial Monitor (which should have been a clue) and had to attempt multiple times to open it.

Eventually, as you eliminate more variables, you narrow things down. Sometimes it’s just luck. Sometimes it’s knowing where to look, and not getting stuck thinking it’s one thing when it’s totally another. I took the bad USB cable, cut the end off, and tossed it in the junk bin, and gave the student a new cable. Everything worked fine then.

Whether it’s troubleshooting, debugging, or just “solving problems” it can take time, and you have to be willing to put in the time. It can be frustrating, but at the end you usually walk away with more knowledge about how to solve problems in the future. I can bet that if something like this happens again the student will remember that one bad USB cable that set back their progress for a few hours.

(I’ve also been working on rescuing a failed Windows computer this week, so I need all the strength I can muster to deal the dumpster fire of an operating system that is Windows 7. I remain convinced that every who says they hate computers says so because they are forced to use Windows.)


T35TP4TT3RN (aka TEST PATTERN) is a piece I created for Maker Faire Milwaukee in 2016. It consists of a Raspberry Pi single board computer connected to an old Sony broadcast monitor. (I got the monitor from another member of Milwaukee Makerspace who was getting rid of old equipment.)


As I often do, I wanted to contrast old hardware with modern hardware. I ended up using a Raspberry Pi Model B which has composite video out via an RCA jack. I used an RCA to BNC adapter to connect to the monitor. The display is a whopping 640×480 pixels.


I used the Raspberry Pi Slideshow technique and with most installations, I tried to do a good amount of testing beforehand, letting it run for days at a time. I came across an issue where the system would freeze, and it would get stuck on an image. I contemplated switching to display of a video, but really wanted to avoid that, so I set a cron job to reboot the Pi every 30 minutes. I figured that if someone saw the screen during reboot it would be an extra BTS sort of treat. (The Pi boots very fast.)


I did end up altering the monitor a bit. I removed the case and broke out a bit of the battery compartment so I could slide the Pi and extra cable into the battery slots. Since I’ll probably never own the batteries for this unit, hacking it seemed like a no-loss situation.

Here’s a collection of a few of the test patterns that were displayed.







One of my PCOMP students wants to randomly select a set of RGB values from a predetermined list. It’s the sort of things where I know the concept is easy but the execution is a bit more difficult only because I’ve done it in other languages/environments, but not in an Arduino sketch.

The nice thing about programming is that once you know how to do something using one language, the concepts transfer over to other languages, and it becomes mostly a matter of figuring out the syntax and method to make it all work.

Here’s an example sketch that allows you to have a list (array) of RGB values and then randomly select one and return it, split the r, g, b into their own integer variables, and then print them to the serial monitor. (The final version will use analogWrite to control RGB LEDs.)

// RandomColor.ino

void setup() {

void loop() {
  char* rgb = returnColors();
  int r, g, b;
  if (sscanf(rgb, "%d,%d,%d", &r, &g, &b) == 3) {
    Serial.print(", ");
    Serial.print(", ");

char* returnColors() {
  char* myColors[6];
  myColors[0] = "128,0,0";
  myColors[1] = "0,128,0";
  myColors[2] = "0,0,128";
  myColors[3] = "255,0,0";
  myColors[4] = "0,255,0";
  myColors[5] = "0,0,255";
  int colorIndex = random(0,6);
  char* result = myColors[colorIndex];
  return (result);

Obviously the list can be much larger than just six elements, but this is example code to be expanded upon.

You can also grab this code from github.

Update: Royce has his own version you can check out. He suggests it should be more efficient because the textual RGB values are converted to binary at compile time rather than runtime.

Teensy BOB 1.4

The folks at Seeed Studio got in touch with me about their Fusion PCB Service and asked if I wanted to try it out. I’ve ordered stuff from Seeed Studio over the last five years or so, and I’ve never been disappointed with their products, and since they offered a coupon to save on an order, I decided to give it a try.

PCB Options

My previous PCB was the Teensy LC BOB v1.3. I ended up making a very small revision and released v1.4, which is the board I used for this Fusion PCB order. I’ve ordered these from OSH Park and they turned out good, so I wanted to compare ordering from Seeed Studio.

I should mention that I am not an Electrical Engineer, but a maker & hacker who learns things by trial and error. I’ve managed to get lucky with the PCBs I’ve ordered and part of that success has probably been due to the sensible defaults that OSH Park uses. By comparison, when uploading my Gerber files to the Fusion PCB service, I was a little overwhelmed. (See image above.) The choices… so many choices! While I didn’t know exactly what every option was, it was easy to choose them and see how it affected the price. Many options caused the price to go up by 2 or 3 or 10 times the amount. This made it easy to decide what not to choose. The one choice that is nice are the colors. OSH Park boards are purple, but you can get Fusion boards in green, red, yellow, blue, white, or black, which is great.

The one tricky form value you need to deal with is Dimensions. By default it is set to 70mm by 70mm, which comes out to $9.90 for 10 PCBs (though they seem to be changing that to 100mm by 100mm for $9.90, slightly better pricing.) You need to input the dimensions of your PCB as they are not detected by the Gerber files you upload. It’s a bit confusing… I guess for small PCBs you can panelize them. I should learn how to do that as it seems you can save money / get more PCBs by doing it.

The $9.90 is the base price for 10 PCBs, but adding more PCBs affects the total cost, but not by much for small boards. I could get 100 of my ATtinyNoisy boards for $18.32. That’s 10 times the number of boards for just twice the price! For the Teensy LC BOB v1.4 it’s $9.90 for 10 and $49.69 for 100. Economies of scale, yo.

Gerber View

One of the things that was missing when I ordered by PCBs was the preview of the board when I uploaded it. Well, either I missed it, or it’s a new feature that was recently added. Here’s what the Gerber preview looks like for my PCB in Fusion.

Teensy BOB 1.4

Teensy BOB 1.4

The boards turned out great. They look amazingly well done, and checking the 20 boards I received they all looked identical.

I actually placed two orders, for the first one I chose the fast shipping option, and the boards were completed within just a few days and shipped from Shenzhen, China to Milwaukee, Wisconsin in two days. Wow. That was for DHL shipping at about $20. Not bad at all.

The second order I chose the cheap shipping option, which was just $10. The boards were completed on November 18th (two days more than the first order) and were shipped, but as of December 4th (16 days later) I still have not received them. They were sent via Singapore Post and should be delivered to Rosemead, California, and then transferred to the USPS for delivery to me. I’m hoping they show up soon. (Update: They showed up on December 15, 2016.)

Teensy BOB 1.4

In summary, I was extremely pleased with the quality of the PCBs I got from the Fusion PCB Service from Seeed Studios. There are a lot of nice options when ordering, and volume pricing can make a lot of boards really cheap. The shipping costs and options are something to consider. With OSH Park the free shipping is nice, but of course you do end up waiting a while for the boards to be produced. OSH Park does have something called ‘Super Swift Service’ which adds $89 to your total. Oh, Fusion also has an “expedited” service that makes your boards in 24 hours, and that’s a $199 charge.

If I get to the point where I need a lot of PCBs for a project, or plan to sell them, Fusion would definitely make sense. If that’s what you need (perhaps for a Learn to Solder kit?) give Fusion a try.

« Older Entries | Newer Entries »



buy the button:

Buy The Button