All Good (And Poorly-Maintained) Things Must Come To An End: The Great Project Purge of 2012

i swear to god i will fix this later

At some point, I need to stop telling myself that. It’s well known that my stuff isn’t exactly world-class in terms of reliability and Six Sigma class in quality, but even I can get sick enough of it to declare it a loss and start over. Over the past few months (and years) of neglect, quite a few of the robots and silly vehicles have become damaged and non-operational. I kept Swearing That I’ll Fix It Soon, Guys, but my shelf of stuff is long past overflowing with parts and project detritus and some of them contain good parts that I don’t want to keep buying. With my general shift of operations towards the newly opened IDC space just up the Z-axis from MITERS, tearing down some of the old derelicts and returning their parts to the Earth (/my storage bins) became more appealing – especially as I started collecting more stuff, most of it landing on my fresh new corner desk.

So it is with great sadness (and hidden catharsis) that I must announce the decomissioning of…

Cold Arbor

Cold Arbor never really worked – the frame was too flexible to accommodate the huge teeth of the saw. After Motorama 2010 and Dragon*Con’s Robot Battles ’10, CA pretty much only ventured off my shelf for the occasional demo – it illustrated, visually, what a “combat robot” was very well. Pretty much everyone’s first reaction at the word “Battlebot” is “You should put a saw on it to cut through the other robot!”, and CA is…. well, pretty much a saw. It never really stopped driving, but then the saw actuator broke so it couldn’t do the extending thing any more. Arbor, being the biggest lead weight I had on my shelf, was therefore the first to go.

But before I tore it totally down, I decided to use it still-functional and very smooth drive base as a test dummy.

Last year in the Austrailian robot fighting circle (did you know that Australia has a very active robot combat scene too?), one of the builders began to modify Hobbyking brushless controllers to act as H-bridges for DC drive motors, utilizing 2 of the 3 half-bridges available on the average BLDC controller. I’ve been advocating something like this for a while – use the cheap hardware base that is Chinese brushless motor controllers instead of custom-developing an expensive niche robot controller solution. The choices in robot controllers these days are either said niche and expensive but generally reliable controllers, or these one-tiny-FET-per-leg overfeatured doodads that I’ve literally had zero success rate with. Or you straight build your own and have them work, but I’ve also not successfully managed that yet. There’s nothing on the market right now which is just a bucket of large FETs like the old Victor 883s (which you can still buy, but they’re now a design so old it can almost drive).

That aside, I have also never bothered to schematic-trace the brushless ESC boards or learn & put up with enough raw Atmel C to reflash the microcontrollers (though I suppose I could have flashed Arduino onto them…). So, a ton of hot air rage on my end, but lots of action in the 40+page thread over on the Robowars forum, which has seen all of the cheap common ESCs reverse engineered and firmware implemented for – up to and including its own confusing beepy configuration menu.

They’ve now started selling them (when I say ‘they’, I really mean like one dude), and I took the chance to get some modified “85A” units based off this Hobbyking ESC.

First, I had to remove most of Arbor’s existing electronics. Okay, so my success rate with the Sabertooth controllers isn’t zero – Arbor runs two of the closely related SyRen controllers, but $75 for 25 amps is stupid these days, and I’m also royally undersizing their loads – one is running a little Speed 400 class motor and the other is running a drill type 550 motor which sees about a 10% duty cycle on raising and lowering the saw.

Way cleaner wiring and layout with the ESCheap85 in – I could easily see a robot with a whole rack of these next to eachother. The massive spam of SMT FETs technique used to great success by cheap Chinese controllers is an acceptable compromise, in  my opinion, between one-tiny-SMT-FET per leg used by the Sabertooth and Roboclaw and other most-likely-designed-by-newly-graduated-college-students controllers, and the one-huge-nice-FET approach I usually take. It keeps the board size down, too.

After hooking this up, Arbor was taken on several somewhat strenuous (and absurd) test drives.

None of it was very scientific, nor was there really enough space to seriously stress the bot out. I’m going to have to use these in battle myself before I’m fully sold on the idea, but based on the reports of the substantial number of Australian users, they’re pretty bulletproof, and a few American users have already run 18v DeWalt drills in drivetrains using them (the same motors that Clocker uses). The 85A type has been praised as a “Victor replacement”, but its more limited voltage range (30V fets and 35v capacitors) doesn’t quite convince me it can be swapped directly into a native 24v (up to 28v fully charged and more during dynamic braking) system. I fully agree with the concept, though, and for about $1 per amp I don’t have any complaints past my own reservations.

That doesn’t mean I’m no longer going to attempt my own controllers – I have yet to successfully execute a small current-controlled vehicle H-bridge, of which robot controller is a simpler subset. But that’s for another post.

At the end of it all, here’s Arbor mid-scrapping:

Scrapping is such a negative word. It took me a while to crack open that weapon drive gearbox, since I sealed it up so well at the start – and some of the bolts were bent.

Here’s everything I ended up keeping from Arbor. All of the motors, pretty much all of the drive mechanics (especially those delicious custom gearboxes, which were one of my first good ones), and of course the saw and worm drive in case I rebuild it all. The VictorHVs and Sabertooth controllers were also kept and filed in my robot controllers bin.

prospect for rebuilding: slim

Arbor was a very complicated robot with lots of moving parts – it’s something which is more difficult to get right, and it’s usually more disappointing (to watch as well as to operate) when it doesn’t work. Arbor’s build was rather rushed and many details weren’t completely thought out. I’m more likely to build a 30lb bot that is either more plainly functional or spend alot more time to build a complex but well-designed and tested robot before trying to compete with it.

Going down the line, next I pulled out…

nuclear kitten 5

NK5 was heavily damaged last Robot Battles, and ever since then has been sitting on the shelf. However, the disc motor still works great – and I can make spare discs, so that’s definitely being reused on something. The controllers and motors were also potential salvage items.

NK5 was the last robot I built before I converted fully over to “T-nut” style construction, visible in pretty much all my stuff from 2009 onwards. The design actually dates from late 2008 – my first major t-nutted endeavor was the ill-fated 2.007 robot. The frame has these wonderful corner bars that I machined for this application, but it seems like now you can buy everywhere. I really liked these, so I went ahead and saved them. Tapping into real metal is way better than t-nuts at any rate.

Here’s NK’s remnants pile. The frame materials were just not worth keeping, but I kept the motors – the gearboxes are not stripped, but one of the pinions fell off (but is intact). They might become donor parts for future gearboxes. I am a fan of these little 25mm metal gearboxen: while they are not planetary, they’re big and chunky inside to make up for it, and fairly cheap at $10-15 each.

prospect for rebuilding: hell yeah

I can’t guarantee when, but D*C 2012 is likely because I pretty much have everything-minus-frame. The disc is up for some revision, though. Big tall vertical disc spinners are no longer in vogue, being replaced by small, low bricky drum things with built-in motors (of which there are now like 50).

Next up is my pride and joy,

test bot 4.5 MCE

Really? The bot that made it to real-deal-Battlebots-IQ, then Motorama 2008 and back? The first thing I ever worked on at MITERS? Yep, since its default parking spot since Moto 2008 has been in Clocker’s lifter when it’s not doing other things.

TB certainly has the most grime of any of the bots, and the lifter was pretty much utterly trashed – it took a direct from the vertical disc bot Igoo at Motorama 2008 (that video is slightly painful to watch).

This is one of my first drill motor hacks. I did a few in 2006 for the original TB version 4, but they were either terrible or dismantled very quickly. This thing predates my entire website, pretty much. The extension shaft with the pinion was added when I redesigned the lifter for Moto 2008. It had an additional outboard support, but since it was made of UHMW, the whole gearbox still flexed too much to keep the gears in mesh, and so the pinion stripped very quickly in battle.

After I took the damaged arm parts off, I realized that TB’s drive base was actually in very good mechanical shape. I still love those gearboxes, too: they are super special 12:1 drill box hacks that I made with mating the salvaged 18 tooth planet gear and 9 tooth pinion gear of the first stage of a drill motor with an intact output stage. Coupled with the extremely overvolted 9.6v drill motors, this made the bot have a rather zippy top speed of 14mph. The first version of this gearbox predates the website (again) – this version at least had the luck of being milled, so things actually lined up!

I briefly entertained throwing the BotBitz ESCs in the frame just to drive it around again, but decided against it for the time being. It’s sure been a long time since I’ve had a 4WD drill-powered box.

So I closed it right back up again. Only the damaged arm and wedge parts were scrapped – otherwise, I think I can put something interesting in this bot again, or at least give it a better sendoff at a serious combat event later on, as the most honorable fate for a combat bot is still, in my opinion, being thoroughly vaporized into a cloud of small particles.

prospect for rebuilding: not for Robot Battles

TB4’s design was optimized for “arena” combat which has more guaranteed smooth floors and a more pressing need for huge, thick angled armor. The RB stage is purposefully left fallow to discourage pure wedges – a passive aggressive attempt at encouraging more robot creativity, which I contend has been successful in the past few years even though it kind of locks me out from competing in 12lbers again there with this design. Maybe Motorama 2013….

Finally, a project that I hate to see get tossed so early, but…

razer revolution

It’s lived a decadent life of being a demo attention whore as well as occasionally coming in handy when Melonscooter was on blocks, and has seen 4 different motor controllers (Double DEC’er, Melontroller, Tinytroller, and Jasontroller!), but recently RazEr Rev has become kind of a wreck.

I donated the front end to another MITERS scooter effort after the new battery got 2 dead cells after only a few weeks – definitely a case of bad initial conditions. Since then, it’s been sort of chilling in a corner, slowly being eroded away by the tides of cruft and dead power supplies that ebbs and floes around the shop.

The Jasontroller works great, the battery can be surgically corrected (I’m literally going to scalpel/X-acto knife the dead cells out and make it into a 10S pack), and the Dual Non-Interleaved Razermotor is a little rattly in the bearings but otherwise functional.

So that’s pretty much all I kept. Oh, and the extra heavy duty generation 2 Razor handlebar, after they moved away from welded-to-frame folding joint but before cost cutting made the joint like 24 gauge steel. This front hinge is massive – the steel is something like 0.13″ thick.

The reason I decided to scrap RREV now is because I’ve become dissatisfied with the frame design. It uses a design which I now consider inferior to other similar scooters in the way it’s put together. Starting over with the frame will be a great way to optimize the design towards less material use (like giant plates of 1/4″ aluminum) and make it simpler to assemble in addition to making dedicated space for the battery and Jasontroller, both of which were “aftermarket” additions. It should end up lighter for the same performance, but I don’t see it getting any smaller. Sorry Jamo, but Razor Wind is a little on the small side for my tastes now.

All this talk of what I’m gonna do means the

prospect for rebuilding: immediate

I already ordered some more giant aluminum plates (…sigh) and will probably be redesigning the frame this week. I’ve already got the changes planned out – they’ll just need execution. Like NK5, it will just be a matter of moving old parts over to a new chassis – there’s otherwise not much about RREV that I’m unhappy about. It’s definitely going to get a stock fender.

other stuff

I didn’t take any pictures, but all the Chuckranoplans have been parted out and recycled too. I’m probably not going to be touching this for a while until I stop being afraid of foam so I can build meaningful scale models. 3D printer models were fun for design practice, but are too heavy to work.

Alright, now that I’ve eaten half my offspring, I can start considering rebirthing them again!

Dragon*Con 2010: The Real Wrapup…Finally.

hey charles, don’t you owe all of us a dragon*con 2010 event report or something?

Yeah, yeah. The beginning of term, lack of motivation, and the lackluster (but entertaining) run of the robots at Robot Battles meant that I just Haven’t Gotten Around to writing up D*C2010. But I seem to be on a streak of making up for missed writing assignments this week with all the site updates, so… here we go.

Welcome to Dragon*Con. If you missed my description of it last year, don’t worry. It hasn’t changed a bit. The atmosphere is still as eclectic as ever, and the crowds just as dense. Actually, they were probably denser. D*C is one of the biggest conventions in the continental United States.

But I’m not a fan enough of anything to really enjoy the con for most of its con…tent. So let’s move onto the robots.

Also, I like girls with big guns.

Right. Anyways, robots.

Like last year (and years past), Southern Polytechnic rolled out their VEX robotics kits and sponsored an open build-off on Saturday. The participation was pretty intense, with young children showing up strongly. At the end, there was a ball-gathering competition.

sunday sunday sunday

Time to stop diddling. The “Microbattles” event is held on Sunday, before the big competition. NK hasn’t been here since 2008… in fact, when this version was first built.  So NK is running 2 years behind the development curve. How have its opponents evolved since then?

Oh…

The robot caliber this year is seriously advanced compared to years past – alot of it, in my opinion, due to the fact that the other Southeastern builders that I used to smash robots with have also now advanced to college machine shops and have become spoiled like me.

I mean, except Thomas up there, who’s just magic.

Cake, from the Georgia Tech crew – another one of the high-caliber machined and fabricated bots.

On the other end of the spectrum are things like this, which are built by people who are just out to have some fun and entertain the crowd.

Speaking of the crowd…

The Robot Battles events seem to always have outstanding attendance no matter what. The International ballroom has a seating capacity of several hundred (the exact number escapes me). At several points during the event, it was standing room only in the back of the room. And at least once, who I can only presume was the Hyatt Regency’s fire code liaison came booming over the room intercom instructing everyone who was standing to leave.

Disappointing, but oh well.

NK made a run through the tournament bracket before being Caked in the winner’s bracket finals. Cake, being a lower hitter, won every collision. I originally was going to forfeit any matches involving the high-energy weapon bots since I was more interested in maintaining NK’s operational status, but hell, it was the finals.

So I went for it. Overall, NK came out pretty undamaged for the amount of ass-kicking Cake dished out throughout the tournament.  No prizes this year, but the finals match was stunning.

Here’s NK’s highlights for the Microbattles tournament.

clocker and arbor

The day after was the big robot tournament.

Dragon Con is my annual robot party, since it’s precisely at the end of summer and represents the last bit of fun I’m allowed to have before flying back for the academic term. So I spend all summer building or upgrading the robots, among other activities, and bash it all up at the end.

This year, I brought both Arbor and Clocker. It’s been a while since I’ve run a 2-robot tournament, but with Robot Battle’s more laid back atmosphere, it wasn’t nearly as stressful as Motorama. In fact, I rather liked it.

Most of the usual suspects were back, with hacks, mods, and upgrades aplenty. Here’s (Big Blue Saw Presents) Jaws. Also back in the mix was Dale, Evil Robotics, MH, Found Objects, and others.

But this year also saw quite a few newcomers. The Armed Robotic Critters, for one, came with a whole fleet of critter-themed 12lb and 30lbers. Overall, attendance this year was back above pre-2009 levels. 2009 was sort of a bad year for the competition due to several builders having to skip the competition.

Then you have Sporkinok.

Really it’s not even an antweight, but Seth brought it (and a 12lber) anyway. Just for Grins and Chuckles™.

Only at Robot Battles…

….does this kind of stuff happen. You know what’s really hard to catch when you’re a 12 pound robot? A 1 pound robot.

I really can’t say enough about the level of audience energy at Robot Battles. The Regency 6 and 7 ballrooms combined sat over 1000 people….and again, during the event, was reduced to standing room only. The event also encourages the audienec to participate by helping start, end, and occasionally judge matches.

Yeah – you don’t come here for SRS BIDNESS TERNAMINT. You come here to put on a show.

Clocker did great for a while, but then immediately suffered another left-side drive failure. What the hell?

A quick examination revealed that the left gearbox output shaft was poorly assembled (read: did not press hard enough) and slipped its interference fit. Now, what was really weird was that shifting the whole shaft axially some times caused it to re-engage just enough to give the robot differential traction. So Clocker ran sporadically, but was crippled at other times. When the drive disengaged, I just threw on a Zip Tie Ratchet.

Here’s Clocker’s highlights video from the competition. I managed to execute another Robocopter spin with Jaws around a minute and some in.

That’s the move I designed Clocker to perform, and it did so admirably. Unfortunately, the clamp motor was unresponsive, so I couldn’t throw Jaws off the stage. As close as it turned out to the camera guys, this was probably for the better.

Oh, Cold Arbor.

As nice as the upgrades I made were, it still didn’t stop the saw from just catching and binding. I pretty much expected that to happen again, since this milling blade was made for multi-ton machines – not a 30 pound robot. Arbor was visually very impressive and garnered alot of audience applause, but ultimately it suffered two losses because it just couldn’t do anything.

If Arbor is to be actually competitive, I’d have to rethink the whole concept of the robot. Right now, it comes down to an issue of severe uncurable positive feedback – the forces of cutting are squarely directed into jamming the saw further into anything it contacts.

If you observe a regular cold saw or even power miter saw in action, you’d notice the saw’s swing is more vertical than horizontal. In other words, the tangential force of cutting is directed perpendicular (or nearly so) to the direction of saw motion.

Arbor’s movement is very horizontal – made even worse by pivoting the saw at the base of the robot. Therefore, the force of cutting is directed downwards and back into the robot, which is the same force vector I’d generate by cranking downwards on the saw with a pry bar. The net result is that any impact of the blade has to be compensated with massive torque inputs – realistically, more than the worm gear output can probably handle or anything short of an Etek can generate.

overall

Neither a win, nor a fail. I went to the event to put on a show (since there’s really nothing to win), and I think the bots did that just fine. I’m still keen on the concept of an actual working saw bot, however, so don’t expect Arbor to just disappear into MITERS. It will be rethought (possibly while I make sure Clocker’s gearboxes don’t let loose ever again, EVER).