Hey, what ever happened to Überclocker?

It’s late July. Why haven’t I seen a robot post yet, Charles!?

Well, too much LOLrioKart and lots of time taken up by my job building Terminators. But ‘clocker has been in the back of my mind for a while. With Dragon*Con and Robot Battles now a month and a half away, though, it’s starting to climb up the list really fast.

In the last Überclocker episode, we left off with the last known CAD drawing of the whole robot.

This was designed back in November-December of last year. Now that 2.007 has come and gone, and I’ve explored building puzzlebots more, I hate this design. There’s too much unsupported sheet metal. Too many things being bound together with a compression member that are otherwise supported, too many parts, and too many awkward assemblies. The overarm mechanism is also shady. But at least the clock logo on the top is cool.

Nevertheless, I needed to use material more effectively, so I opted to redesign the frame with large, T-nutted members alongside interlocking tabs.

So here’s a picture of the rework in process. The drive base part count was reduced 25%, and this goes together alot more like my other robots. Otherwise, everything remains the same – gear and chain-based 4 wheel drivetrain, and the Integrated Dual Frankenb0xen™.

I elected to switch from 4.2AH lithium polymer batteries to a small cluster of A123 26650s. A123 cells are renowned in the model and hobby robot industry for almost absurdly high performance (pulse discharges up to 60C and continuously to 30C or more) at the cost of a bit of energy density. The biggest upside is their comparative nonfinickyness.

The pack configuration I chose is 7S1P, or about 25.2 volts charged and 20 volts discharged. This is the closest match to my existing 22.2v electrical system.

A leap of faith later, and the bot is mostly done. The overarm is still from the last revision and is just there for visual effects.

The fork has been drastically simplified. Instead of cut plates, I decided to go with plain standoffs retained with allthread or long bolts. It turns out that using these standoffs with the binding pressure of good bolts is actually stiffer than the spans of aluminum I have been using in the real bot and the designs. It has the highest stiffness-to-weight ratio of the options.

But now it won’t look as badass.

The new overarm designed. Looks kind of like the old one, eh?

It’s slightly narrower and not as “huge”. The width is because it precisely fits the clamp actuator in the middle with little room to spare. Also, the overarm no longer hinges from the main fork axle, but rather is a fully independent assembly. This will save assembly time and simplify field repair, since I won’t have to rip the entire front half of the robot off to service one part.

And here’s the clamp actuator. Gee, it looks kind of like the last one.

That’s because it is. But it’s better. And won’t suck – I promise.

The difference lies in the fact that this one is substantially larger. It uses a Banebots 28mm planetary gearmotor driving a leadscrew nut, which rides up and down a stationary and larger leadscrew. While normally I shy away from Banebots equipment, their newer motors seem to be decent and the output shaft won’t be taking any direct shock loads, only gear torque. They’re also available in a reasonable voltage, unlike the next best option (screwdriver motors) and aren’t enormous (drill motors).

The leadscrew will be firmly (read: either threaded, pinned, or set-screwed-with-big-flats) embedded in its own hinge block, so we won’t have the problem of the clamp arm falling off and jamming the leadscrew under the robot.

I vouched to retain the leadscrew design because of the degree of isolation it gives between the arm being forced upwards and the force on the motor. The clamp is an enormous moment arm for anything on the end to push against, and if there were a direct 1:1 rotary coupling between the clamp arm hinge point and my actuator, I could very well blow something up.

Additionally, the fork is attached to the main shaft using Ginormous Death-screws. Like set screws, just more hardcore.

On the other hand, having the leadscrew means the only way the mechanism can be defeated is if the leadscrew bends, the threads in the nut strip, or the arm breaks in half. I’m ruling out the possibility of 5/16″ diameter hardened steel shoulder screws shearing. One of these shoulder screws might be replaced by a nylon or Delrin rod as a last-ditch overload lifesaver.

The frame, demonstrating gratuitous T-nutting. I purchased square nuts from McMaster expressly for fulfilling this role. It’s like an end-tapped hole, but there’s no drilling, tapping, or setting up the part which is inevitably impossible to hold properly as you drill it.

Another time-saver on this robot was my discovery of shaft collars with bolt circles. Seriously – shaft collars with threaded bolt holes in them, to attach something to a rotating shaft. That’s called a hub. If you only tighten the shaft collar a little bit, it’s called a clutch. If you combine the two, it becomes a torque-limiter.

So I have simplified the Great Cone Clutch Clusterfuck to use this one awesomecollar. Currently, the main fork shaft uses two shaft collars acting as clamps over a split tube to transmit torque to the fork, to great effect.. I expect a direct connection to be no different.

Covers. The clock logo is not yet laid in, but the main feature of the top plate is visible. It’s actually three plates. The center one is directly over the battery pack, so I can get to it and swap packs very quickly. Because the pack is only 2.3Ah, I’ll probably need to change batteries (as opposed to just charging in the bot) for quick turnaround times.

Either way, removing 9000 screws to get at one loose wire in Uberclocker was too much of a PITA to repeat.

And so it begins.

You’re looking at about $300 of McMaster hardware and $200 of other crap (wiring bits, controllers, motors). I don’t know how these things got so expensive (damn economy, etc.), or maybe now I’m just building real robots or something, because nothing I used to build cost this much.

Maybe this is just a symptom of my encroaching laziness. Hey, why build things when other, smarter and more productive people have figured out a way for me to buy stuff from them?

I got a nice enough deal on the 4 Victor 883s that I’ll probably end up using them in the bot, even though they are enormous and will take a pretty good amount of stuffing.

It’s time to excavate the robots and prep them for rework. For the past year or so, the bots have been on the bottom shelf of a multi-deck pushcart upon which I have heaved all my spare parts, random cruft, metal billets, and half-baked projects. They were really really dusty.

I’m actually considering keeping most of Überclocker 1 assembled, because there’s technically nothing wrong with the bottom half of the robot. The frame and running gear are still functional, and technically the lift gearbox still works – one motor just smells weird. Since I’m not really reusing any parts at all, it would make a good “audience bot”. Hell, if the upper clamp arm is removed, it works fine as a spatulabot.

Alternatively, anyone want a half-robot? I wouldn’t mind selling the current build to generate more parts money for the current one. Sans receiver, but including 2 Victor 883s, a Victor 36HV on the fork motors, and the LiPo batteries (with external balancer connection using a DB-9 connector).

The chassis metal is on the way, and with my waterjetly ways, the frame ought to be assembled by next week. Kind of good, considering next week is the last week of July.

Bot…on?

The Summer Build Season 2009

It has begun.

While I seem to be in “build season” mode year-round, it is during long breaks with little in the way of academic or life obligations that I get the most done. Last summer, I began work on LOLrioKart and built Überclocker, Pop Quiz 2, and Nuclear Kitten for Dragon*Con.

… which sort of sucked horribly for everything. Except NK, but only by about *this* much.

So what’s coming down the projectubes this summer?

Mostly the same thing. D*C is my biggest bot-celebration of the year, so once again the combat robot fleet takes high priority. Since there’s really just one robot that needs rebuilding, I also have the usual pile of small electric vehicle projects, of which only one is actually urgent.

Übercløcker RЭmiχ

I started redesigning Uberclocker some time in the fall of last year, hoping to get it done by Motorama 2009. Of course, due to scheduling concerns and logistics, this didn’t happen. But what that presented me with was the chance to put it away and not look at it for several months.

This is pivotal. The basic design has already been hashed out, but now I get to return to it after not thinking about it for a while. I am now in the process of analyzing the 3d model for any “impossible objects” that I might have included, or Really Bad Ideas. Such design flaws plagued the real life Uberclocker 1.0 at D*C last year.

Planned upgrades from 1.0? Well, besides EVERYTHING, the primary focus is on drivetrain reliability, center of gravity, and the upper clamp arm.

As a member of the pushybot school of combat robotic thought, I value maneuverability and driving above jawesometacular weaponry. Uberclocker 1.0 had a strange serpentine timing belt setup that seemed like a really awesome idea at 5 in the morning, but… wasn’t.

The robot also suffered from “centrally located center of gravity” syndrome at the event. While a CoG near the geometric centroid of the robot is good in practically every other case, the fact that the bot’s sole purpose was to grab another opponent and lift it off the ground meant that it just sort of faceplanted every time I attempted a lift. Not a very impressive show. The redesign lengthened the wheelbase of the bot, and selective weight reduction moved the CoG back about 4 inches, without additional ballast.

Oh, that’s right, Uberclocker 1.0 weighed in at an incredible 22.5 pounds out of 30 at the event. I’ll fix that too.

What I didn’t really get to (properly, anyway) in the redesign was the upper clamp arm. The previous arm was both weak and structurally unsound. While I think I took care of the “unsound”, I still have my doubts as to the clamp mechanism’s effectiveness.  In the past, clampbots have used pneumatics to actuate the upper half of the clamp. This is advantageous because a pneumatic actuator requires no “holding power”, unlike an electric motor, which has to be continually powered to produce torque. Pneumatics also have a certain amount of spring-back ability that a solidly coupled electric actuator doesn’t.

But robot-heaven forbid that I make Überclocker even more complicated by incorporating a pneumatics system for the one actuator that might need it. Thus, I’m still partial to a (spring-coupled) leadscrew-type mechanism, over the current design candidate’s motor-on-a-weird-gear. Except this time it won’t be driven by a beetleweight motor.

I intend to keep the “Chinese puzzle” frame, and will be refining it for ease of assembly. I devoted a few weeks to just fabricating the frame parts last time – no, never again. That’s what computer-controlled machine tools are for.

Pop Quiz 2√2

Incidentally, 2√2 is about 3. Not quite there, which also describes this planned rebuild of Pop Quiz 2. It’s not quite a complete conceptual revision, but there will be significant upgrades all around.

PQ2 is one of the (if not the) flattest 1lb class robots around that has an active weapon. It hits lower than some undercutters. The problem is that going the extra 1/8″ down in this current design meant that I had to ditch practically all the well-known, battle-proven parts – Sanyo gearmotors, SPEKTRUM 2.4ghz receivers, etc.

It was a fun thought experiment come to life, but the robot had a horrific reliability record, almost no reception due to the FM ground-band receiver, and a 5 minute chopped hack of a master power switch that ended up disintegrating after exactly 1 hit at D*C 2008. Pop Quiz had about 15 seconds in the arena.

Not cool. For ’09, I am INCREASING the height of the bot. Me, making a robot taller. How many times does THAT happen?

The robot height will be increased to about .400″, enough to cram in a set of real Sanyo micro gearmotors. The rest of the robot’s electrical system is sound, and so is the weapon motor. I’ll most likely end up reusing the electronics anyway, minus the cheesy little FM park flyer receiver. Instead, it will be swapped out with the latest Spektrum DSM offering, and I will run one transmitter between all the robots.

There’s no current virtual model for PQ2.8284171, but just imagine the current bot 0.025″ thicker.

Nuclear Kitten 5.1 Digital Surround Sound Edition

I’m actually satisfied with the performance of one of my combat ‘bots for once. NK needs very minor rework to take another run at D*C. The weapon motor needs some magnet reglued, and the weapon pod pivot axle is slightly bent and needs to be made better anyway. Past that, I have a spare blade to replace the faceplant-into-steel-bumper bent blade.

The only point of concern with NK is the drivetrain. Despite having a mechanically isolated weapon, I’m still blowing drive gearboxes, just because the bot is that much more powerful. I might switch to something like the 50:1 Copal motors || redesign the motor mount || use softer wheels.

No frame changes are necessary, since the bot escaped D*C rather unscathed.

LOLrioKart

Since I discovered that the main battery pack was leaking voltage all over the place (somehow, through an eighth inch of rubber?), I stripped down the entire electrical system and tested all the batteries. It turns out that the steel casings of the cells are live, something which I’m fairly certain should never be the case. While it’s fairly common for the battery negative terminal to also be the casing, the errant voltages are always somewhere between 0 and 1 volts.

This case voltage doesn’t seem to have negatively affected the cells, but I’m fairly certain it’s the culprit behind stray frame voltages. Somehow.

The focus for LOLrioKart work will be the electrical system. I intend to complete and test the ginormoFET controller and possibly implement dynamic (or regenerative!) braking using the upper leg of the half-bridge. Mechanically, the kart is fine.

Well, except for the brakes, but they’ve always been undersized and insufficient.

Ultimately the goal is to run it for longer than 1 minute on all 54 volts, or the full pack voltage of whatever eventual power system I might come into. I’m heavily considering crating up LOLrioKart and shipping it down when Dragon*Con comes around, so I can drive it in the parade. This could possibly be the worst idea I have ever thought of.

Project RazEr

It’s been hanging on a utility hook since the last controller fire. Everything works and the batteries are still charged, so all I need is a BLDC motor controller. Since everything still technically “works”, I don’t intend to touch the scooter that much, if at all. Any work on it will be replacing the shell of the wheelmotor with something more substantial (and better engineered, and more reversably built).

Time to get crackin’.