Archive for March, 2016

 

The Overhaul 2 Design & Build Series, Part 1: How to Overhaul a Design

Mar 07, 2016 in BattleBots 2016, Overhaul 2

Here we go! The very first (real) post in the Overhaul 2 Design & Build saga, which will set the stage for the future posts. What I’d like to do with this post is give a little more story on how Overhaul 1 was designed and built, its shortcomings in the competition, and then move onto how I think the new build should address those issues. Then, from here on, the posts will be exclusively design and build oriented. My anticipation is that Parts 2 and 3 will be very long, showing the evolution of the CAD model, and from there, the posts will be more scattered with build updates and interspersed with CAD updates.

The first step in evolving a new design is always to appraise the functionality of the old, and to do that, it’s time to review what made Overhaul 1 into what it was for Season 1. In the first portion of this post, I basically summarize the build process for Overhaul 1, so that’s worth a read. What you never got to see in that post, since it was made prior to the airing of Season 2 episodes, was the competed design and the near-completion bot. We weren’t supposed to reveal anything yet, much like how you’re not “supposed to” be doing now.

So here’s some never-before-seen pictures of the build of Overhaul 1. First, the finished CAD model:

There’s the beast in its entirety, designed using Solidworks 2014. Trying to twiddle this model a year after the fact has caused me to forget much of its hacked-together behavior, and additionally made me wonder what the hell “midline axis of fancy thing” was (it was the central axis of the leadscrew nut on the top clamp arm…)

Documentation. We has one.

Recall the photograph in the “Life of Charles” post which shows megatRON mated to Uberclocker.

You can basically break down OH1 into three components. The front (leftmost part of the CAD model), which is the dustpan/corral of Ron, the upper arm and clamp which is heavily Überclocker, and the shuffler modules inspired from Fission Product. It was largely designed in this manner, with the four of the principals (J, A, me, and D) moving from ‘station to station’ with the design.

We basically knew from the start that nothing about this design would be ‘optimal’ due to the genetic confluence and conflicting design requirements. So the design was kept very modular on purpose. The drivetrain was one box, the dustpan was another, and the arm stuck on top. The positioning of everything ended up being dependent largely on where internal components had to go, which is a theme which will return for version 2. This ended up giving Overhaul 1 it’s very characteristic “hunchback” look in the arena.

Not only that, but the wheeled drivetrain seen in the tournament matches in Season 1 had to be made to fit entirely in the space previously occupied by the shuffle modules, resulting in the wheelbase being very short – only 10″ on a bot which was 41″ from end to end. It might as well have been 2WD!

 

While this made for quick turns, it meant the bot had no front traction centered under the massive front dustpan, and furthermore, was already very front heavy with the lifting arm and its 2 actuators (plus the top clamp arm) hanging off it. The little black and white ball below shows the center of gravity – as you can see, it started past the front wheels.

When we got anyone on the forks, it was often at the expense of being able to, you know move. And then there’s this embarrassing shot:

This, coming from someone whose bot was known to do the “robocopter” was borderline shameful. This goof was a result of putting the large rubber shock isolators (“wubbies”) in a straight line at the dustpan’s interface. We just kept it to the height of the bot frame for convenience.

Contributing additionally to traction issues was the large overhangs of the drivetrain caused by the switch to wheels. The shuffle legs could reach well past the “wheelbase”, but wheels, obviously, were limited to the contact directly under them. This meant that there were plenty of moments where OH1 was lifted up backwards – either by opponent attack or counter-torquing the lifting arm, such as the first Lockjaw match below, where I couldn’t get out of it without lowering (or being lowered) back down.

OH1 could really only be tilted back about 15 degrees before losing rear traction, and this was a key issue in why we lost the Bite Force match (besides my too-aggressive tactics, which is not really a design problem so much as a firmware issue with me). Any time Bite Force got under me with some energy, it was enough to prop OH1 off the ground.

Besides driving, the arm itself was too slow – watch OH1′s matches again and you’ll see quite a few missed lifts. I’m used to the very fast lift of Überclocker, and the linear actuator driven arm was a great deal slower than that, and lack of practice really hurt my timing.

The reasons why we went linear actuator over rotary (e.g. Bite Force and some other lifters like Stinger) was partly due to available parts and partly due to lack of experience. It was our belief at the time that you couldn’t get a gearbox heavy duty enough to handle the torques – many hundreds of ft-lb – without it being massively heavy or requiring another stage or two of torque amplification to use, which also increases weight. A linear actuator is a cheap way to get immense force at the expense of speed. In fact, Overhaul’s lower lifting fork could lift well over 2500 pounds at the maximum current of the motor, accounting for the 85-90% efficiency of ball screws. That was basically unnecessary, and should have been traded for speed somehow. Another factor was convenience – the clamp actuator and lift actuator were fundamentally the same parts, just one with a bigger gearbox.

There’s another detail which influenced the ability to grab and lift effectively. Look at where the forks end - well inside the tips of the triangular pontoons. They’re tucked in largely in the interest of anti-spinner protection – we didn’t want the forks to be the first thing a horizontal kinetic weapon hit. This also led us to make the “backboard” for the portion of the arm which dropped down into the dustpan.

It was kept that length also due to an unimplemented feature:

The crossbar at the front of the dustpan was going to be 1/4″ AR400 grade steel bars with some 1/4″-wall steel tubing and ribs backing it up. Not only would it have greatly increased the rigidity of the dustpan, but it would also have visually completed the bot, giving it more of a reason to occupy its nutty 42″ total length. One guess as to why we left if off…

By the way, after the tournament, I realized it was much better that it got left out. The triangular pontoons allowed OH1 to get a proverbial foot in the door in most of its  matches, where the broad surface of the crossbar might have prevented it, and also prevented more of the opponent from reaching the arm.

Can you guess the reason yet?!

In the end, besides “fundamental design flaws”, we never really had any major problems with the build or the tournament, and we frankly had a reasonable time with maintenance.  We got skilled to the point where we could pull a drive motor in under 5 minutes with tools ready, or the entire clamp arm assembly in the same time to get to the actuators, which was what we were doing when I was interviewed for the 2nd Lockjaw match; they had a penchant for bugging us for interviews and talks exactly when we needed to do something. It was definitely not “designed for service” in many ways, but we got good at it to make up for the part access deficiencies. It helped that OH1 was not very dense – a lot of it was air….

….but someow it STILL weighted 253 pounds out of 250 when done. Yup, no front crossbar for us.

So let’s summarize.

  • Overall, the completely unoptimized design, prioritized for a fast build and ‘unique combination’ of predecessor bots, led to a number of inherent flaws. When you glue 3 robots together in CAD, and have that be the point of the build, there will be parts of each bot which won’t work well with the others.
  • The lack of front traction under the dustpan section hurt maneuverability with an oppnent under control. Either I could try to push against someone or I could lift, but not both; at least, not very well.
  • The wheel were not pushed far enough towards the edge of the body to grant the bot sigificant rear traction. We tried to work with the existing spacing of the shuffler axles and used large wheels, both contributing to the short wheelbase.
  • The rubber shock mounts were used in bending instead of tension and compression like they were designed for. The result was an overly flexible dustpan that folded when the bot attempted a lift
  • The lifting forks were too slow because of the use of linear actuators. The lifting forks had superfluous force that could never have been used effectively.
  • The lifting forks did not project out of the dustpan, meaning the bot could not initiate a lift first. I could only drive under someone and try to maneuver them towards the arm.

Therefore, we can now designate a set of goals for Overhaul 2 that will resolve these problems.

  • Overall, the design must flow together and each part must have a reason to be in the place it is.
  • The chassis must either extend under the dustpan, or the dustpan must be affixed to the chassis in a way that allows a drive wheel to bear the lifting load; at least, the center of gravity should be between a drive wheel and a stationary contact with the ground, or best, between two drive wheels, as seen from the side.
  • The wheels must be made smaller to be pushed towards the corners, or the frame must have cut angles to permit tilting back; preferably 30 or 45 degrees or more. (Überclocker has wheels that ‘poke out the back’ for near universal traction)
  • The rubber shock mounts should be used in compression and tension as much as possible to mount the dustpan.
  • The lift system will be driven by a rotational actuator like a geared motor instead of a linear actuator; speed of lift is critical in being able to control opponent traction.
  • The lifting forks shall protrude from the dustpan profile, or better yet, be modular to be swappable to a short or long configuration as needed.

With these factors in mind, it was time to begin playing with concepts. We begin with the first concept of Overhaul 2, drawn some time in July 2015:

I’ll explain myself, don’t worry.

Presenting the Overhaul 2 Design and Build Series

Mar 03, 2016 in BattleBots 2016, Overhaul 2

FARUQ TAUHEED MODE

LAAAAAADIIIIIIIIIIIIIIIIIIES AND GENTLEMEEEEEEEEEEEEEEEEEEEEEEN, IT’S ROBOT…

END FARUQ TAUHEED MODE

…blogging time.

Greetings everyone, cat ear guy Charles here with an exciting new muscle-building, fat-burning workout pl…. wait, wrong commercial script. You know, I’ve just been drowning in fame and commercial endorsements and guest appearances since Battlebots season 1 ended and all. Yeah – don’t even get me started on the Great Hot-Dog-Bounded-Pizza Debacle of 2015 – I’m gonna NEED a workout plan after that one. Conveniently enough, #season2 is just around the corner, and you know what that means! Accelerating the deterioration of my lumbar vertebrae by another 25 years!

Sardonics aside, welcome to the Overhaul 2 build report series. If you’ve been a consistent reader or browser of my website since 2007, you’d know that I really enjoy documenting every part of my project builds as they happen, week by week, or even day by day. If you haven’t been a consistent reeader or browser of my website since 2007…. well, I really enjoy documenting every part of my project builds as they happen, week by week, or even day by day. Hello. I do not enjoy long walks on the beach.

And I really mean it; not only do I highlight the successes of my projects, but also the failures, the mistakes, and the could-have-beens. Nothing is hidden, glossed over, or excused. That’s because over the past roughly 10 years of etotheipiplusone.net (wow…), I’ve helped create a culture of project documentation and build blogging amongst my peers, first through the MIT student club MITERS where weird project people like me flourished, then later on as an instructor for the MIT electric-vehicle-building classes of my own design. This website, and by these indirect extensions and influences, has helped formed the core of a small network of  well-documented projects in the electromechanical realm, and have served as resources to many hundreds, if not even more, projects; I’ve only heard of or been told of via e-mail a few hundred of them, anyway.

By its very existence, it shows that making things isn’t all praying and summoning spells – it’s a dirty, involved, some times convoluted and counterintuitive process that you have to go through to make your project work. Nothing is magic and everything is machinable™ .The fact that problems are dissected on this (and others’) websites are what differentiates them from project galleries or “selected works” pages.  This is not a pretty portfolio site, and that’s by intent.

Which is why I’m taking significant time out of the activity of actually building the robot to tell you all about it. The truth is, this runs directly contrary to what the big shots at ABC, who fund the production of BattleBots and give it air time, want me to do. For months now, builders have been under a veil of secrecy which is just now being lifted in controlled ways. They want exclusivity and popcorn-spilling movie trailer structured hype. Well, if I had it my way, I’d have been posting about Season 2 since last November, each step of the bot’s design evolution and each one of the changes. I held off because the process would necessarily have entailed exposing the final robot design prior to the loosening of the leashes, and I didn’t want to fuck over the BattleBots producers.

My sole mission and agenda for #season2 is to make Overhaul 2 the first open-source BattleBot (with a capital B) and to inspire throw head-first onlookers into pursuing careers or hobbies in the engineering & making fields. Sole. I don’t care about huge multinational media conglomerates, and I don’t care about toy deals or book deals… though let’s face it – this build series will be a very well-sized book. I care about telling the world that the glamorous, sparkling mechanical violence they’re watching is not beyond their reach, and that each and every bot in the series was built by real people who all started somewhere, some not very long ago.

Engineering and science in pop culture is constantly presented with a little dog-shit of whipped cream on top and a wave of the hand, and my goal is to throw that right back into the money-greasy line kitchen that made it, in the only way that I know how – by not holding back when I fuck up. Overhaul 2 will be the most involved and complex engineering work I’ve embarked on to date, and you’re going to see every horrifyingly bad weld and questionable choice of hardware. Here’s what “open source” will entail:

  • First, a series of posts which chronicle the design process from the first sketch to the latest complete configuration – spanning a period roughly from last November to just a few weeks ago. Expect the first one soon!
  • Next, I will attempt to update at least weekly – if not more – with photos from the build process and explanations of what is happening. The current date is March 3rd. There are only 5 weeks to “ship date” at this point, so expect some rapid-fire posting.
  • Finally, to the limit that I am permitted to and which will not spoil tournament results and the TV episodes, I will chronicle the leadup to the event and activities at the venue itself, hopefully day by day, with more details after the season finishes airing in separate posts.
  • And lastly, after the dust settles, I will upload all of the design files and documents associated with Overhaul 2. Every CAD model, technical drawing, parts sourcing invoice, and last minute hasty edit will be available.

Like with Chibikart, the intention is not to spawn a hundred clones of the bot (Good luck sneaking that past the entrant selection for Season 3, right!?), but to push the technological bounds and the design space of the sport. There’s a lot of new things I’m planning on trying, and some of it terrifies even me. I’m not afraid of sharing full designs, because no matter how poorly you clone something, in the end, you were forced to build something even if it was missing one critical detail that real life copy-paste didn’t include! That’s basically how 2.00gokart worked. If Overhaul 2 throws a hundred new builders into the wider sport because Dude, I didn’t know you could do that with a Harbor Freight 18V Nose-hair Trimmer w/ Flesh… Flashlight Attachment, then I’ve succeeded on my terms, even if it loses its only match.

Before we begin with the juicy details, here’s the social media promotional kibbles you should Like & Subscribe and back my kickstarter (Oops, that already finished…)

  • First, let’s get the 800lbs of Gorilla Glue in the room (that’s the saying, right?) out of the way. Team JACD, the boy band, as you knew it during Season 1, is splitting into 4 indepdendent bot efforts for #season2 and onwards. Check out the JACD page for the information!
  • My “branch” is Equals Zero Robotics, and I am adopting the Overhaul design. The Facepage will be more “up to the minute” and casual; photos posted to it will likely end up here in a long-form post later on.
  • The unlocking of publicity and creation of E0R has finally forced me to update Equals Zero Designs with information relevant to RageBridge 2! Product stuff will all live on Equals Zero Designs. RageBridge 2 will be available on E0D and Robot Marketplace in the coming weeks!

And that concludes my pre-season angry rant. You can tell that the forced secrecy is a thing which has really been nagging on me, since it really is antithesis to what I am set out to do. I’m genuinely NOT out to spite the network or shit on the presentation. I bite the hand that feeds me for its own damned good; that’s my story, and I’m sticking to it.