It’s Robot Season! Time for a tiny Überclocker. The Announcement of 12 O’Clocker

Wow, how’s it almost the middle of August already? You know what this means?

That’s right. Basically, for the past few years, every late July and all of August has been spent rage-prepping robots for my annual robot party that I’ve gone to compete at since…

2003.

Holy shart, this one better be good then! And what better way to make it good (…besides having functional robots for once, I mean…) than returning to the 12lb class from whence I came?

It’s been a long, long time since I had a functional 12lb class bot. My parting shot at the class was in early 2008 with Test Bot 4.5 at Motorama 2008. At the time, the NERC Sportsman 30s were just barely becoming a thing, and after that event, I decided to participate in the class instead. The 12lb class at the time was just becoming infected with the “Brushless Penis virus”, in which builders rely increasingly on spinning larger and larger chunks of tool steel with larger and larger brushless motors, leaving the class designs polarized towards either those or heavily armored boxes without other redeeming features. Matches basically came down to who got in The Hit first and often ended with both bots being disabled or otherwise gimpy and hobbling.

It’s like being a dubstep groupie – always about The Drop, but with robots, so half the match you’re just waiting for The Drop and talking for days afterward about how brutal The Drop was while picking splinters of A2 tool steel from your forehead.

That game got boring for me fast. So, I spent my next 3 distracted years building dysfunctional versions of Überclocker, until last year when I finally seemed to manage something remotely interesting.

With Überclocker Advance seemingly performing up to snuff at Motorama 2013, and only needing very minor repairs and upgrades for this year (to be detailed soon), it was time to think of new robots. If I were actually good about sketching out my designs, what would follow is a small thesis worth of fantastic fun machines, none of which would actually qualify for conceptrobots.blogspot.com.

But what I really want is a tiny Überclocker. Ever since version 1 back in 2008, I’d wanted to scale it back for the 12lb class. This hasn’t ever happened yet since I’ve had enough fun getting the actual Überclocker to work properly. I’ve also thought of doing up a beetleweight or antweight version. Past that, the thing which has kept me from developing the idea further is that I was reluctant to build a bot for one event: Robot Battles is the only event I am aware of that has a “sportsmans 12lb” type competition – even though its own competition is much different and came way, way before the modern era of robot fights. Events like NERC Motorama would force me to run this elaborate contraption with the brushless pen0rs.

I’m not sure when I decided to actually pull the trigger on this design. Originally, I was hoping to make a grand comeback with Test Bot 5. I’ve completely designed Test Bot like 17 times over since 2008, but the basic flavor has been the same – a 4-bar lifter with a solid and fast drivetrain. Sadly, this is as far as I got on the last ‘redesign’:

Not even sure what I was getting at any more. Oh well. Those saw motors aren’t even available now.

I figured that all of my fresh-built bots will have some kind of weird teething issue if I start this close to the event, and that would be quite an embarassment to the Test Bot name. I’ll bring that back when it’s ready. Maybe having a 12lb Clocker would encourage the development of the 12 Sportsmans up here quicker – there’s been plenty of talk about it, of course, but we just haven’t quite hit critical mass yet.

Like Überclocker Advance, I jumped into Inventor and made up a quick sketch just to get the dimensions down and see what might fit where. This is where this entry will degrade entirely into CAD pictures!

This skeleton drawing was made about 2 weeks ago when go-kart season was in full swing. Part of what I wanted out of this bot was a bit of ridiculousness. After all, it’s a small Überclocker, and any good chibi version of an existing thing must emphasize its best features. This bot was going to be all fork – or at least the fork will prominently feature in the design. The body will also be shrunk into something with a higher aspect ratio for a bit of the goofy look.

I had in stock several 2.5″ “McMasterBots” wheels – the 40A type – for what I can only imagine was the next Test Bot, so I elected to start the design with this element, even though I think it would have also done great with 3″ and 4″ wheels. Some times, you just need to “ground” the design somewhere or you’ll never start. So this bot will be tall, with tiny wheels (but still plenty of ground clearance), and a giant fork.

One question I had which I tried to solve early on was what to use for drive motors. In the 12lb class, if you’re a pusher type, drivetrain-tensive bot, a set of 500-class motors is about the norm. When “hobby tool” sized cordless tools were easily available in the early and mid 2000s, four of them with their RS-380 motors made a typical first bot for many folks – and Test Bot’s third incarnation which last competed in 2005, and should still be around here somewhere, still uses them. I really wanted this 12lb Clocker to have a forceful drivetrain, since it would likely need to travel around carrying an opponent.

Speedwise, my choice of wheel size precluded using even the 24:1 single speed cordless drills – it would have been dirt slow. I was spoiled by Überclocker Advance’s near-20mph top speed and excellent handling with the 40A wheels, and I wanted something similar for this bot. I briefly considered a set of Vexboxen, but at my required ratios for direct drive (wheel-on-gearbox) it would have been too long with a motor, and would have made the bot like 16″ wide – almost as wide as 30lb Clocker.

Space-wise, an external chain reduction similar to the near 1:1 indirect drive of 30lb Clocker was the most feasible, since it meant I could keep to a single speed gearbox. To minimize size, I decided to make my own gearboxes:

The hell is that? It’s what I’m calling the Angerbox. Like Vexbox and Ragebridge, and other similarly pissed-off sounding robot parts. What it really is is a 3D printable case that holds half of a drill gearbox. Similar to what I did on Test Bot back in the day, cutting a drill gearbox in half and (preferably) using the all-metal output stage nets you a 6:1 reduction. What you see there on Test Bot’s motors is a 2:1 spur stage feeding into the 6:1 planetary output stage, creating a 12:1 gearbox that gave Test Bot a nice 15mph top speed.

I plan to implement that roughly 2:1 reduction using the chain drive this time. 6:1 direct on my 2.5″ wheels would give a top speed of like 25mph, which is a little over the top, but would burn out the motors quickly.

Here’s the Angerbox placed in the frame for first sizing passes. I also drew in various sprocket pitch circles to see what ratios made sense. In the end, I settled on an external 14:24 drive, yielding, with the 6:1 planetary and anticipating overvolting the 18v motors (since I have an asston of working motors with destroyed gearboxes from Null Hypothesis) to 8S (25v), to get me a top speed of 18mph.

Why a 14 tooth on the motor? It was the smallest sprocket that had a hub big enough to enlarge to 12mm bore (drill shaft size) and have enough meat left to hold a big set screw thread. Most times, “the math” doesn’t take these physical considerations into effect – this is one of the big lessons I try to get across in my Silly Go-Kart Camp, that you can math until the end of the world but your project still must exist physically, which implies other constraints.

A 12:24 would have been a clean 2:1, but the sprocket would have been so small that attaching it to the drill shaft would have been damn near impossible without machining the drill shaft down to size (weakening it greatly of course…)

I imported the old drill parts from Test Bot’s CAD files (after cross checking with my bag of drill parts to make sure I actually had the correct types), so here’s what the mostly finished angerbox CAD looks like. The stock drill shaft will be cut down to fit in the bot. The case will be a quick 3D printed jobbie (Hey, the drill cases are originally made of shitty plastic anyway, okay?)

Using my 2D drawing as a visual reference, I started designing up the actual parts. Unlike all the Überclockers ever, this design will feature “overhung”, or single supported wheels. I tend not to favor them, but both weight and goofy looks might force me to use them this time. To make up for the single support, the axle pins are huge for a 12lber: 0.5″ aluminum to be made with my left over 7075 stock. A little bit of overkill, but the fatter the axle the less bending they experience for the same load.

At this point, I’m just trying various different layouts of parts to see what makes the most sense. The batteries, just a single string of A123 26650s, dominate the decision. I decided to make the frame tall enough such that they can stand fully upright, or else the square footage of the bot was going to increase drastically.

Hmm, I *could* make the bot longer and ditch the sloped rear to gain a bit more interior volume. This was, again, one of about 5 or 6 ways I arranged the parts before moving forward.

Another config again, still with a flat back. This was the frontrunner for a while…

Until I realized that with a flat back, 12lb Clocker was hopeless if flipped over, which it fuckin’ will be, most definitely.  That made me switch back to the sloped sides, and it also made the bot’s profile more symmetrical. This design would allow the rear wheels to touch the ground just a little to putter me around for a quick escape. I’ve moved on to the more important parts now – the fr0k. Other elements such as the drive chain tensioner (imported straight from 30lb Clocker, mostly for placement and looks) and the clamp actuator have also been rough-placed.

This clamp actuator has quite a history. I made it all the way back before Dragon*Con 2008 for the the original Überclocker when my previous design failed in testing right before departure. Between this and the imported 6:1 gearbox idea from Test Bot, this bot is bringing back some serious history! The original 20:1 (or something) small gearmotor on it was stripped, so I replaced it with a 9:1 HP Pololu motor. This thing was the first custom linear actuator I built, which made me go crazy afterwards with the Cold Arbor actuators.

I’m going to stick a stock 36:1 HF type gearbox on fork duty since I have many of them and they can be easily converted to all-metal gearing because of the identical 6:1 stages. That and because I need all the reduction I can get for this dumb fork. A 60 tooth sprocket is the output stage, driven by a 13-tooth sprocket on the drill shaft.

Why 13 teeth?! This size sprocket is small enough, and the spacing of the drill motor serendipitous enough, that I’m just tapping it for the 3/8-24 thread on the drill shaft and threading it the fuck on there. A 12 tooth’s hub is too small and a 14 tooth doesn’t get me as much reduction.

With the almost-5:1 reduction from the 36:1 box, I’m still looking at 150 rpm on the arm shaft. This is something like 10 ft/s of linear lift speed. Fast enough to be used as a really bad hammer!

The motor will be mounted by some 3DP’d clamps that conform to the shape of the gearbox. I designed this part to be serviced just like 30lb clocker – four screws and the whole motor can drop out the bottom. No more removing 75% of the bot to fix one thing like last year, ever.

Getting close to the final appearance here. I’ve added a first-pass geometric model of the clamp arm. I literally picked reasonably random numbers for the rise and slope of the portion where it attaches to the fork. Brought it in, see how it looks, and change if needed.

This is, of course, another lesson I try to teach in Silly Go-Kart Camp – at some point, you gotta start putting your design down and stop trying to solve for every dimension analytically before you open Solidworks. Once you have a starting base, then you can adjust and optimize dimensions and placements based on constraints and whatnot. That’s why I just started throwing rectangles at trapezoids at the beginning.

Too many times I’ve witnessed people sitting while staring blankly at sketches on a piece of paper and an empty CAD screen, not knowing what to start designing first. The answer: all of it. Right now. Or I will fail you.

I went through quite a few iterations of the clamp motor placement, too, before realizing the best position is basically where I had it first. In this position, the motor is well out of the way of the action and the leadscrew length can be kept short, which in this bot is critical for weight.

Notice the Clampy Shaft Collars of Unintended Power Transmission. I’d use the stock 3/4″ flange collars on McMaster, my favorite for go-kart steering linkages, but they somehow got EVEN MORE expensive. And they’re steel.

Can’t do that on this bot. I just bought some aluminum clamp collars and will just drill my own damned holes in them, because when you average it all out I make like $9 an hour anyway and I know drilling 6 holes is going to take less than 3 hours.

Getting a little more detailed up front now. I’ve added the leadscrew attachment joint and the lower fork standoffs. The leadscrew will be anchored directly to the fork this time – it will be a little harder to disassemble if I JUST need to get to the anchor, but the screw itself will be easily disengaged with one epic set screw. This is for simplicity and also weight savings.

Clocker’s “reactive outriggers”, or its spring loaded leggy things, are kind of its trademark. They’re also responsible for the various tricks it can do to opponents, like driving while clamping them or twirling them in circles.

On 12lb Clocker, a discrete ‘shock absorber on swingarm’ setup would be unnecessarily heavy for how rigid it needed to be. So I had a bright idea of making a flexure leg using a stick of spring steel as a leaf spring.  It only took like an hour, 2 FEA simulations, 3 Wikipedia pages, and a few MATWEB searches to do what amounted to a simple bending-beam problem, but using what’s available in the McMasterBots catalog, I found that either a 3/32″ or 1/8″ thick 1075 steel strip that’s 1/2″ wide will work. The 1/8″ was a ‘worst case’ estimate of a 12 lb opponent hung all the way out on the end of the fork and the legs deflecting no more than 1/2″ at the tip.

So what do I use? Well, I just bought 1 strip of both and will make both of them. I really want to see how this bot drives on one or the other before deciding.

Attachment-wise, aluminum machined anchors hold the spring to the body of the bot, and it passes under a standoff extension of the front axle pins, starting the bend at that point. Kinda-sorta – the “roller” constraint means it will actually start bending before then, but the distance from the standoff to the anchor is short enough that I don’t think it will contribute significantly.  At the tip, another machined anchor will be bolted to the steel and have a little ball roller riding on a shoulder screw coming off it.

To machine the Rockwell C44 spring steel, I snagged a cheap F size carbide stub drill off eBay since finding this around campus will be less than likely (nor do I want to ruin someone’s $50+ carbide drill by being too enthusiastic with it!)

Quick overview shot now that the major geometries are in place. Out of a practicality concern, the fork isn’t as stag-beetle-esque as I had originally hoped for.

At this point, I imported 30lb Clocker for a size comparison. Clocker is a huge 30lber – by footprint, it’s larger than some classic 60lb Lightweight Battlebots. This is due in part to the need to contain most of an opponent, and a long wheelbase/wide track make for greater stability once contained. So Clocker has never been very dense.

12lb Clocker is a little better in that department, but it’s still pretty big for a 12lber. It’s a full 14″ wide and 9″ long if you only consider wheels, and this isn’t too bad, but this increases to 17.5″ from back of wheels to front of fork.

With major parts complete, I checked the simulated weight: 11.4 pounds including the top and bottom armor, which are not visible in this picture.

Oh boy. This is without wiring, without modeled chains, and without most big hardware. It’s time to start “gothic cathedraling“, as I call it. Since these plates are going to be waterjet machined, I only have “cut through” or “not cut at all”, so things will look pretty spider-webby when done. First to go is the big sprocket.

Before starting on the “cathedraling” proper, I designed in all the corner gussets and final top/bottom armor attachment points. The torsion box up front and the gusseted C at the rear are very similar to how 30lb Clocker is set up.

The “cathedraling” this time is mostly X trusses, nothing too special. For kicks, I decided to add a simulated chain, and boy am I glad I did.

I totally forgot that, even though there is a pinch roller tensioner in the posterior run of the chain, the anterior (front) just goes straight down. And intersects my frame rails.

A bit of modification to that area later and I was all set again, only gaining back like 6 grams.

Cathedraling complete, and now with top and bottom covers mounted, including the huge obnoxious 12:00 cutout up top.

Why 12:00? Because it’s 12 o’clocker!

I really want to get a big EL panel kit and put it behind the cutout and have it blink 12:00 like an old VCR or broken alarm clock.

The weight as shown is 10.6 pounds. I’m now within the realm of possibility for making weight after factoring in the rest of the hardware.

The last detail I needed to address was the chain drive. The tensioner I imported straight from 30lb Clocker would work just fine, except the wheel placement would have caused the bottom run of the chain to hang like 1/4″ below the frame bottom! That’s just asking to get snagged on something and broken, leaving me stranded (again).

Not allowing that to happen. I rerouted the chain over two smaller roller tensioners such that for the most part the undercarriage is clear of chain runs. If weight allows, I’ll put a 1/8″ polycarbonate or other lightweight shield over this area to prevent accidental mishaps.

Here’s a better size comparison between 12 o’clocker, Überclocker Advance, and the 2008 version of Test Bot. So I guess 12 o’clocker isn’t really that big – TB was a full 12 x 12″, plus a few more inches of wedge and lifter arm.

Since the kart class caused my updates to run behind schedule a bit, I’ll put out a spoiler: The parts for 12 o’clocker have already been machined, and I can hopefully assemble most of the bot this weekend! Also on deck is a report on 30lb Clocker’s new clamp actuator, and more info on the D*C Robotics Track panels I intend to do this year.

 

Colsonbot Rage-Finish and Bot Blast Recap

Well, here it is! Colsonbot was finished in the intervening 3 days between the previous post announcing its arrival and when we all shipped off to Bot Blast. The event was a blast indeed, and I’m furthermore glad we even got there in the first place! Here’s the whole story.

This is the friction drive module fully assembled. A little printed rim attaches around the motor, around which I sling some stretched-out O-rings. I recommend everyone who is considering O-ring friction drive make sure that the rings are not bought “on-size”, since if they are, at high operating speeds they will stretch out and be more likely to pop out

Tension in the friction wheel mechanism is maintained with a stack of wave washers. I was hoping for enough space to put a very short coil spring, but it ended up that I really only had 4-5mm to play with. So, wave washers it is.

Since this bot is way more unibody than anything else I’ve built, I needed to construct most of the wiring harness first before installing the motors. Here are some of the Pololu 30:1 HP “Sanyo-flavored” gearmotors being prepped with wires. I call these motors “Sanyo flavored” since originally the first on the market in the robot world was the 75:1 Sanyo micro gearmotor.

Other electronics being prepped include two Vextrollers, one of the left over 18A ESCs from tinycopter version 0, and a gutted Hobbyking receiver. Everything had to come out of their packages for this bot since the space was extremely tight.

The wheels are also 3D printed affairs. They’re little duallies made with O-rings. The center bore is pre-flatted to mate with the Sanyo motors with a set screw hole on the flat to keep them secure.

The installation sequence is wheels on motors, then motors into their mounts.

The center shaft of Colsonbot is a single hollowed-out 5/8″-18 fine threaded bolt. The hex head was machined down to 1/8″ thick, and it rests flush with the top of the battery cavity in a hexagonal cavity which prevents it from turning as I tighten the clamping nut.

Wiring on the bot can be described as “ad hoc”, to keep it politically correct. I used no connectors at all – there’s not enough space for the ones I had. To reverse motor directions, etc. meant desoldering.

Most of the wiring is done with 30 gauge wire-wrap wire, with heavier currents such as the brushless controller and two Vextrollers done up in 24 gauge.

First power test! This was just to verify that everything was still working and hooked up the right way.

Starting to add the other snappy-lids to keep things constrained. The electronics are mostly just piled inside the cavities. I had thought of making little exactly Vextroller shaped cavities, but realized I would never have put up with that level of cleanliness. It’s just a little too Apple.

Lids attached. The external wire run is unceremoniously held down by a glob of used Kapton tape harvested from the Hobbyking battery.

Time to put everything together and find out exactly how not a 3lb bot this is. Turns out the answer was not even 2 pounds. Great…

I knew Colsonbot would have a not-enough-weight problem since it could literally be made of lead and be fine. There’s just not enough volume of bot inside the wheel. Colsonbot’s base by itself, at 10 ounces, would actually make an excellent 1lb shell spinner with a 6oz real shell. This is something I’m considering for Dragon*Con, now a little over a month away.

With a second 5/8″-11 jam nut and a bit of thin PETG plastic, I made this direction indicator since otherwise I had no idea which way the bot was facing underneath!

And here is the soft underbelly!

Check out some of the test footage:

Colsonbot being  a roughly square 4WD setup, handles extremely well and it’s also quite peppy. It really does not need this many motors. As can be seen in the video, it “gyros” extremely easily due to the large spinning mass. I originally wanted to put a “mast” up high over the wheel so it could flip back over, but I decided to keep the wheel illusion. If Colsonbot gets flipped, it will tend to stay upside down and wobble like a coin.

This work was done on Thursday evening. I left Colsonbot alone after that to help out with the two new stragglers we inhaled: Jaguar (by the way, check out his excellent Instructable on his even more excellent Orbit Wheel pod things) and Julian. Of these two, Jaguar decided to start a new robot some time around 1AM Friday.

bot brast

Great, now we’ve increased from four to six people. I was really getting worried about Mikuvan’s mechanical integrity at this point – six guys and another hundred pounds or two of robot gear times 800 miles round-trip plus mountains. If I was going to grenade something, it was going to be on this trip!

On Friday afternoon, I gave the engine cavity a more thorough check over. My primary focus was on the timing belt, since I had observed some leaking oil on the front underside of the engine, leading me to think leaking camshaft/crankshaft oil seals, which would throw oil all over the belt and cause quicker deterioration. Otherwise, I had already done a mechanical once-over after the Adafruit Adventure. To my surprise, the timing belt cavity was dry and there were no signs of abnormal wear on the belt, and the tension was still good. So where the hell was all my oil going, then?

That’s the back side of the engine where it mates to the transmission. I see a new sludgebunny colony is starting to form. This is the area I cleaned a few months ago to see where the oil leak was, and… well, this just tells me it’s coming from everywhere. The side of the block is still well-coated in grunge.  I definitely have no idea where this could be originating from. Valve cover gasket? Rear crankshaft seals?  I’ll write it off to built-in underbody corrosion prevention for now.

Since after the New York trip the oil level was low, I topped off this time with some heavier weight oil – some Mobil synthetic 10W-40 (the manual calls for 10W-30). Time to see if those “for high mileage engines” claims have any merit. The slightly more viscous oil might reduce the rate of runoff if nothing else.

Whatever the case, it was time to ship out. Space Battleship Mikuvan was temporarily commandeered to become the MITERchan Party Van. Having only like 105 original HP and surely less available nowdays to push 6 people and robot gear, this was pretty much my most conservative road trip ever – essentially spent all at less than 70mph and almost all in the right lane. If you know me well, then you know this is basically the opposite of my usual style. The van is teaching me some humility.

Somehow, 6 hours later, Waffle House.

Every time I wander out of New England, I must stop at a Waffle House, so this time we met up with aaronbot a hour outside of the event venue at a Waffle House in Scranton, PA.

On site at the event… and there’s more than one Colson! On the left is Agent Colson, built from a 6×1.25 wheel – it’s flatter, but only 2WD, and also direct drive from a small outrunner. Colsonbot was originally going to be a DD from a large diameter (e.g. multirotor motor) outrunner, and that idea is still being entertained.

Check out the lineup of newbie bots. From left to right is Glorified Doorstop, DEL-RAN Bumble (by Dane), and Speed Bump (by Jaguar). Don’t let those eyes and zip ties fool you – the front of the bot is to the right. I’m glad that somehow in the last week we managed to generate an entire Battlebots team.

Motorama should take walk-up registrations like Bot Blast, because hell if you could get MIT students to commit to anything more than 1 week ahead of time. Trust me on this one.

The event was held in a regional mall, nestled between JCPenney and Payless Shoesource. Quite a contrast of venues from the typical grungy warehouse or barn you find these ‘bot events in. Because of the proximity to curious onlookers, the audience was pretty steady and numerous for most of the day.

I don’t have as many pictures of everything this time, since I was either sleeping under a table or filming matches (And I’ve posted random robot pictures dozens of times). But here’s Agent Colson after one of its first matches, where it may or may not have hit the ceiling. Sad…

The box is a nicely build 12 footer which fit beautifully into the mall’s… band pavilion? Free Speech Corner? Not sure, but it sure worked well.

Colsonbot in line for its first fight…

Colsonbot performed flawlessly during this match (of course it didn’t win anything), but afterwards I noticed the weapon motor was shifting in its slidy-mount. The motor was chosen as a compromise – the one I purchased from Hobbyking that was intended for the bot just didn’t fit. I used instead a Hacker A20-50S, which was admittedly undersized.

It didn’t get hot enough to burn out, but it did get hot enough to warp the ABS housing, causing some tension loss in the friction drive. I literally bent it back while the motor was still hot.

Both colsons being serviced in some way…

In my second match, I sort of went for broke at the end and tried to keep spinning. This resulted in the motor melting the ABS to the point where the friction wheel just sort of welded into its mount, stopping Colsonbot. I still had drive ability, though, so spent the next half minute just getting punted around.

Colsonbot suffered no particularly permanent damage at Bot Blast, and was a great first version run. Now that I know how this version performs, I can better build the Next Generation Colsonbot.

Boy, some “joke” this has turned into.

For Dragon*Con, Colsonbot will return. I’m currently thinking this as the list of changes:

  • 2 motors, since 4 was a bit excessive, and O-ring belt drive to mimic the stable 4WD drivetrain
  • Fitting the larger and more robust motor in the bot as a result
  • Possibly switching to tinyESCs or something to kill the electronics volume even more.

Finally, here are Colsonbot’s two matches from the day!

Returning from the event was entirely uneventful, save for a short section of I-84 in southern New York which seemed to climb straight up a mountain for 5 miles. I realized it was hopeless after fully opening the throttle, falling back into 2nd gear, and was still losing speed. That stretch was done at 40mph with the heater fan on full as I watched the engine temperature climb slowly towards hot.

Clearly, I am never going on a cross-country roadtrip with this contraption as is – I will never even make it over the Rockies, and if I take the southern route through Arizona, would just light on fire regardless. By the way, Newburgh’s Stewart Airport which we passed next to is the site of the original Three Legendary Derpy Van showdown.

So now that Bot Blast is over, it’s time to start prepping for Dragon*Con. More on that later. The final thing to take care of is…

build your own colsonbot

Here’s the entire Solidworks 2013 CAD folder for Colsonbot. Also included are the ready-to-print STL files for all the major components. You’ll need:

  • A Hacker A20-50s or similar motor
  • An appropriately small ESC for the motor – I used an 18A Turnigy Plush
  • Four Pololu 30:1 micro HP motors
  • Two Vextrollers
  • A 3 cell lipoly battery, this one in particular is known to fit (but only if skinned)