Showing posts with label Mindstorms. Show all posts
Showing posts with label Mindstorms. Show all posts

Building The Gunslinger

Hey y'all!
It's been a long time since I've produced new content, and I'm back with a freshly redesigned blog and a fun new robotics project. I've been itching to make some things happen with my EV3, so I buckled down and built the Gunslinger. As far as introductions go, I'll let the video do the talking.


This bot was built mainly from the EV3 set 31313, with borrowed parts from my NXT 2.0 and Technic Excavator (42006-1). The goal was to create a color sorter that did something different; most of the ones you see stem from the model created for NXT 2.0, where the balls are simply loaded into a trough depending on the color. But what if we did something stupid, like shoot them at colored targets instead? It sounded a lot more fun to me, so I got to work. Here's some behind-the-scenes challenges I faced in the R&D process, which the video won't tell you:

A problem I immediately knew I would face was the programming. In the past I've always favored designs where the mechanism does the heavy lifting, leaving the program as simple as possible, and this was a serious step up in complexity. I had to get comfortable with using a Numeric Array variable in the program to store the color values of the balls, since it loads six at a time, and then read the Array one value at a time and do math based on the turret's current position to figure out where to turn for each shot.

Another issue was that I wasn't sure how to have the color sensor read the balls in quick succession, as I originally planned to have them all go down the belt quickly, with no interruption. The risk was that if two balls of the same color went by one after another, the sensor wouldn't read them as two separate balls, and that would skew the whole thing. To remedy this I added a little regulator gate, just a simple parallel linkage with some appendages on top, which catches the balls one at a time and tells the color sensor when to do its thing.

Perhaps the most annoying mechanical problem was designing the track so that the balls would roll easily down into the clip, while still allowing the turret to rotate freely. The turret actually moves the end of the track when it rotates to the furthest end of its range, and it was really tricky to hook it up so that the loading track would slide back into place when the turret reset.

The loading hopper was annoying as well, because a common problem was the balls getting stuck in it before they even reached the conveyor, or jamming in the end and falling out of the machine when the conveyor tries to lift two at once. It was surprisingly difficult to build a hopper that minimizes clogs, but after about three unsuccessful attempts I got one that works pretty well.

Think we're done, right? No, you still have to calibrate it!

The Gunslinger uses preprogrammed trajectories, meaning you have to set the targets in the right place in order for it to hit them. Basically every time I set it up or move it for whatever reason, I have to run it several times using multiple of the same color ball in a row, so I can move the target and get into just the right spot.

Filming the video brought with it its own struggles, the main one being that I wanted to have a clean background, but I don't exactly have the materials to do so. I ended up using two pieces of white foam board (yes, I only had two) and meticulously moved them around with every shot to create the illusion of a closed set.

After all that, you've got a mean, color-sorting, ball-shooting machine!

This one was a lot of fun to build. I hope you enjoyed it, and I likewise hope it inspires you to go create something awesome!

Happy Building!

Happy National Robotics Week!

April 5-13 2014 will be the fifth annual National Robotics Week.The event is recognized in many different ways, often by the holding of a robotics-related activity or event. For details and information about events nationwide, visit the Robotics Week site.
The purpose of the event according to the official website is as follows:
  • Celebrate the US as a leader in robotics technology development
  • Educate the public about how robotics technology impacts society, both now and in the future
  • Advocate for increased funding for robotics technology research and development
  • Inspire students of all ages to pursue careers in robotics and other Science, Technology, Engineering, and Math-related fields
You may notice that this is only the fifth year in which this event has taken place. In fact, it only became nationally recognized in Congress on March 9, 2010 in House Resolution 1055, "Supporting the designation of National Robotics Week as an annual event." In fact, the resolution attributes the purpose of the event to renowned science fiction author Isaac Asimov, as stated below:
 "Whereas the second week in April each year is designated as 'National Robotics Week', recognizing the accomplishments of Isaac Asimov, who immigrated to America, taught science, wrote science books for children and adults, first used the term robotics, developed the Three Laws of Robotics, and died in April, 1992: Now, therefore, be it resolved..."
In preparation and celebration of this week, I have not only been working with my Lego Mindstorms sets, but also reading several of Asimov's sci-fi novels. I encourage everyone to find their own ways of commemorating this week, whether through reading, building, or attendance of an event. Happy Building!
DARPA's  Atlas robot, which is being developed for rescue applications.

The Gear Train of Doom

Sometimes it's fun to create something completely and utterly pointless. Then, after you create something pointless, you want to share it with the entire world, right? Maybe not. In any case, I want to properly display one of my great feats of uselessness: The Gear Train of Doom. The principle is simple. It consists of lots of sets of gears stacked against each other, such that the gear reduction reaches ridiculous levels.
This gear train uses seven 40-tooth-to-8-tooth pairings, and nine 36-tooth-to
12-tooth pairings, with a few 24-tooth gears in there for some reason.


Here are some stats:
  • The gear ratio is one billion, five hundred thirty seven million, seven hundred thirty four thousand, three hundred seventy five to one, or 1,537,734,375 to 1.
  • When driven by a Lego RC motor, which can operate at 3000 RPM, it would take two years and four months nonstop to finish one rotation of the output.
  • When driven by a Lego RC motor, the output has 20 million, 755 thousand, 396.46 foot pounds of torque, which approximately equals 27,131 Chevy Silverados. With that kind of power, one could easily snap the Empire State Building in half. (It would take decades, though).
  • When driven by a Lego NXT motor, it takes an abysmal twenty five years to complete a rotation, but has nine times as much torque as the RC motor.
  • Under no circumstances would you need to use this. EVER.
I built the Gear Train of Doom when I had spare time in shop class, out of the forgotten remnants of a few Mindstorms NXT's. I pretty much raided every gear in the box to build it. My gear train became quite popular among my classmates, and my teacher even mentioned it at a meeting once. (My shop teacher is awesome, by the way. You can find his YouTube channel here). The conversation went something like this:

Other Teacher: "I wrote this great new assignment to make students calculate gear ratios!"

My Teacher: "I have a student who does that for fun, except REALLY OVERKILL."

I think he almost passed out when I showed him all the numbers I calculated. In spirit of this, I encourage everyone to build something completely useless, as time well wasted is not wasted at all.