So here we go – now that Part 1 has had some time to sink in, and now that my shop is looking remotely functional again, it’s time for some part two. In this section will be the two new ‘sections’ (carried over from part 1):
- Operation GIVE ME A BRAKE: Brake system and inspection all-around on Mikuvan!
- Pad Thai Doodle Ninja, an Antweight 4-bar pushybot I designed and built in like 72 hours!
- The trip down, the con, and how the bots did at the event!
- The links and documents associated with my two panels at Dragon*Con.
Yeah, it’s going down about like that. Unlike the last two academic terms (January – August, basically), I’m not “running” a class this term, so it’s going to be way more chill. I’m not sure if I will want to run back-to-back design classes again like the consecutive 2.00gokart and “2.00GLP”, since the overall level of intensity and chaos is extremely high. I see how the department can go through design class professors rapid-fire now.
Anyways, back to the trip. It’s Tuesday night! Time to load up robots.
…but first, I need to get my 200 pounds of tools, accessories, and spare parts out of the back. I left a spare tire, van-specific tool box (like my robot-specific toolbox, but everything is bigger!), and spare fluids. The floor jack was removed since there is a bottle jack for tire changes in a rear compartment. Basically I was purposefully blocking myself from doing any roadside extensive work – I think I’ve gotten everything mechanically to the point where a failure necessitating deep dissection is practically going to be catastrophic in nature and not something I’m going to do in a parking lot.
Replace all the van kibbles with robot kibbles. I guess I could have kept the van kibbles in the back anyway, since I was initially expecting more bots and parts. This stuffing was, consequently, not as epic as the Motorama Stuffing or the Last Dragon*Con Stuffing (though those vehicle did have less hatch space to begin with). The ship-out time was essentially midnight.
Around 4, we reach Flushing, New York, where Xo Has Joined Your Party. This is where the trip got a little more interesting.
In 2007, before I was a wee bunny at MIT, my parents and I drove up to visit the place. We took I-95 in all of it’s forms through DC, Baltimore, Philadelphia, Newark & New York City, then up through New Haven and through Rhode Island. My only memories of the trip are of how I-95 was utterly depressing in every way, from tolls to traffic to construction, and the general level of suck the Northeast urban cluster exhibited.
Six years later, I was meandering up the Bruckner Expressway in the wrong direction when I hazily decided that maybe I-95 wasn’t as bad as I remembered. Plus there was like an exit for it right there and if we kept going semi-lost I’d end up back in Connecticut. So, down 95 we went, across the George Washington Bridge (slowly, because construction and late night truck traffic), and down the New Jersey Turnpike, the fancy Delaware Bridge thing, then down onto Baltimore and onwards.
I’m glad to say that 95 is every bit as depressing and repulsive as I remember it and that nobody venturing out of the Northeast to anywhere should ever drive on it for any reason.
All together, I think between Queens and Baltimore I busted $35 on tolls alone, not even including the relatively minor tolls in Massachusetts. Every bridge or turnpike had its own toll authority.
I thought the Interstates were supposed to be full of FREEEEEEEEDOOOOOOOOOOOM.
In the Baltimore-Washington area, I stopped at my favorite IHOP in College Park, MD. This has been the focal point of several Otakon trips. South of Baltimore, we hit what I like to call “Facebook traffic”, where congestion is so bad and traffic is so stop-and-go that everyone is on Facebook complaining about it. This took about 2 hours to sit through because we came in at the exact time to hit traffic in both metro areas. How are you actually supposed to get to work?
We hit Atlanta around 10PM, for a trip duration of essentially 22 hours, many of which were spent fucking around with the abomination that is 95 in the Northeast Corridor. For instance, it took about 45 minutes to even get out of New York. Then factor in the fact that the cruising speed of my lovely pallet of cinder blocks was about 65 to 70mph.
We journeyed a little off campus to get lunch, and in the parking lot of the local small sketchy college restaurant cluster was an Audi R8. Like most expensive cars, it was parked “haphazardly”.
This year, since I brought actual working robots, and because Pad Thai Doodle Ninja was completed the evening before the con really kicked off, and because I wasn’t trying to speedball an entire new bot in 3 days,I got a lot more wandering and people-watching time. I was especially tuned to try and find people with costumes that looked like they required some amount of mechanical construction or engineering (see my brief on this last year).
That, and giant Totoros.
Here’s a good example. This funky gun-like prop had a ton of lovely CNC aluminum work. The wielder, though, wasn’t the builder.
I spy a little of waterjetting on some of those interior parts!
The thing I’ve historically liked the most about Dragon*Con over other gatherings is that there’s no particular theme. The con covers about every niche of culture, up to and including robots. You’re not even going to find that at PAX or Comic-Con. This enables people to mash together different story universes and characters with much more impunity, for the amusement of all… such as Portalmau5 up there.
I’ll be honest – this is pretty much the only reason I went to the actual con for, besides my own panels. No, not just any group of girls in costume (that’s so last year), but specifically one series. The latest thing I’ve been fanning over is Monty Oum’s RWBY, also known as “Charles has to build shit that Monty designs with ill regard to constant-volume systems”. Most of the characters are Action Girls with giant mechanical transforming weaponry – what’s not to love? The thing that hooked me at the beginning was the RED preview.
The series so far has really pinged my “defer judgement” sense, since to me it seems a little hurried plot-wise and is seemingly laundry-listing TVTropes (site left unlinked because I don’t want to sink everyone’s productivity for the next 11 days) on purpose. But I’m proud of my ability to cherrypick favorites very specifically, so I’m still into the series for the giant mechanical transforming weaponry.
The series is so new that I wasn’t sure if anyone was into it enough to plan costumes, and I wanted to get a sense of what is already out there in terms of mechanically actuated versions. Conclusion? Zero. On the internet, and in real life at the con.
That’s where I come in.
…not right now, though. With Saturday winding down and the Robot Microbattles just around the corner, it was time to intensively practice driving. This was the remains of a laser-cut quadrotor frame that everyone’s 1lbers and 3lbers were beating on throughout the evening. I also repaired Colsonbot by printing a new motor mount carrier and replacing a stripped drive motor.
This year, Microbattles got the entirety of the International ballroom at the Hyatt Regency Atlanta. In past years, the event has only gotten half the space, and the audience had to be capped every time. The event size is now on par with the main Robot Battles, with even more entries.
So many, in fact, that single elimination had to be used for the tournaments again, and we still ran overtime. The event has been running against its time limits (and beyond them shamelessly) for the past 2 years, and this year was no different. Hopefully the D*C planning committees finally recognize this.
The Atlanta arena returns! This year, an actual 12″ sanding disc was mounted on the spinning turntable. I’m glad to see that my contraption is still functional. During the event, it produced quite a few light shows from bots being stuck in the hole, and reduced the diameter of a few wheels.
The usual suspects were in attendance. Here’s the table of G3 Robotics & Variable Constant & Guy Who Never Updates His Website.
This is a reasonable approximation of the audience during the day. The added seats and projection screens helped crowding immensely. Because the arena has a pretty high bumper rail (3″ or so), and it’s up on a stage, you can’t actually see the bots from the audience unless something exciting happens, so it’s entirely dependent on the video crew!
Because the Antweight tournament was single elimination, sadly Pad Thai Doodle Ninja only got one match in, against the veteran Segs (pic from years past, to the left). Cynthia put up a valiant driving effort, but the lack of “lifter lip” on the arm meant it had a hard time getting under Segs, and the bot was twice as slow as originally planned. Near Chaos Robotics, filmer of events, recorded the match in two halves: Part 1, Part 2.
In the rumble, PTDN got into the thick of it and pushed a few people around, then got pinged a few times by DDT. The lifter arm was bent up, but the bot otherwise had no permanent damage and still drives.
Showing why extending the front armor to the floor might be a bad idea – check out the crimps on the left side. After the DDT damage, the bot had trouble maneuvering on the floor.
Rear view of the damage. Because DDT pinged the arm while it was partially up, the force ripped the rear link out of the arm. That part was extremely thin-walled to begin with and should have been thickened, but I was afraid of it interfering with the robots’ self-righting. Turns out that wasn’t a problem.
I do want to fix up PTDN and upgrade the drives to the original 10:1 spark motors I had intended, and redo the front armor. The lifter servos will either be consolidated into one higher torque metal gear servo, or two digital servos for better range matching.
Colsonbot, sadly, was unable to colson much because of the unrepaired damage from Bot Blast. The “duallie” O-ring wheels were beginning to come apart, and the O-rings tended to slip off and get caught between the shell and the bot. It survived the event pretty much unscathed, however, and I don’t intend on making any big changes to it save for remaking the wheels into single-o-ring affairs that have more ‘stretch’ on the rings themselves to prevent them from twisting out. Colsonbot got in one match against Radiobox, and also the Beetleweight rumble where it was mostly a stationary arena hazard.
Back in the Invention Studio on Sunday night, preparing for some final tuning and drive testing. Null Hypothesis had to have a drill motor replaced, but otherwise, I didn’t have to do anything to the bots for once.
At the event, while I was testing Null Hypothesis on the stage, it randomly blipped and stopped moving. The cause was traced to the controller completely losing its gate drive power supply for some reason. Whatever the case, it necessitated an in-field replacement, which Adam is handling.
Most of the builders are seasoned & flavored veterans, but there were some rookie builders this year. It’s good to see the sport grow organically, if not somewhat slowly. This bot is an alleged 12lber – according to the builder, it weighed 14 pounds when finished. Oops! And hence, it was named. It ran without any top armor at all – something which ended up causing it to lose to 12 O’Clocker.
Omegaforce returns, with more unique wedge attachments. The outer and inner wedgelets are linked together in such a way that the outer set lifting upwards for any reason causes the inner set to drop down to the ground. The upper wedges can swing all the way backwards. So it’s a multi-tiered defense system against oncoming opponents. The actual functionality was a bit spotty.
Non-rookie builder (I met Miles at Motorama 2013) but first Robot Battles event. The center of this bot was supposed to be a lifter, but some things didn’t happen in time. And yes, it’s entirely made of wood. I was hoping to face this with Überclocker, but didn’t get that chance.
Another rookie bot that was supposed to have an attachment in the middle (in this case, a hammer) but Stuff Didn’t Happen.
Überclocker 30 charging before matches began.
12 O’clocker after its first match, which I won. I learned that the springy legs worked well, but they were not well constrained downwards and could get pushed to the point where the front wheels of the bot were propped off the ground. The contact point they make with the front axle standoff should probably be modified to capture the leg in either direction – up or down.
This is probably the most quintessential robot even picture I’ve ever taken. Equipment all over the table, Mountain Dew everywhere, and “beasting food” as I like to call it strewn about.
I try to post audience pictures of Robot Battles every year, because it really is a phenomenal show. I think the audience averages 5 or 600 people and can peak near a thousand. In quite a few years that I remember, the hotel had to deny people entrance because it became standing-room only and exceeded the allowed occupation of the room. Here’s the right half of the audience…
And the left half.
Oh, this was before matches started.
I’m extremely proud of the bots’ performance and reliability this year, as well as the show they put on. For my 10th (!) Robot Battles it’s quite refreshing to have things that worked. The robots ended up losing only due to my own mistakes, or my tendency to favor a good show over winning at this event. I actually can’t bring myself to just drop someone off the edge cleanly with the Clocker pair, and this did bring about my own downfall a few times…
Regardless, Überclocker 30 got 2nd place in the 30lb class, fighting Null Hypothesis (oops…), Overthruster , Null Hypothesis yet again, Jaws – probably my most favorite Clocker match ever, Overthruster for the nth time, and finally losing again to my eternal nemesis Nyx. Overall record of 4/2. There were sure lots of reruns this time around. Clocker was a crowd favorite in the past, and now even more so since it works pretty reliably. At the very end, during the rumble, I did lose the drivetrain completely, most likely due to the solder joints breaking off the motors – this has been a weakness of the bot since Motorama ’13 that I forgot about until now.
12 O’Clocker finished what essentially is 3rd place, since the winners’ bracket finals loser and the losers’ bracket finals winner were the same bot. In the final match, I just got plain outpushed by a more powerful and faster opponent. 12 O’Clocker was also a crowd favorite, possibly more so than Überclocker itself, if I could judge the audience well, and went 3/2. 12 O’Clocker’s match videos: Tetanus Shot 1, Oops, Omegaforce, Apollyon, Tetanus Shot 2
So what’s next for the robots? Besides the odd demo or sparring match, it’s time to make the upgrades for Motorama 2014 next February. Überclocker’s current form debuted this past February at Moto ’13, and I don’t anticipate making any changes to it at all (except for actually using the Quick Disconnect style terminals on the Dewalt motors, maybe…). The new actuator on Überclocker’s clamp worked as I expected – I could grab and hoist up opponents very quickly, and the multistart leadscrew eliminated the binding it was prone to perviously so I no longer had to be gentle with the stick – RageBridge took care of the “endstops” by entering current limiting mode. On 12 O’clocker, I want to better secure the front legs, but otherwise, the bot incurred no damage from this event.
the way up
I decided to be intelligent and finally take a route which I’d been eyeing for years, but never dared try for some reason until now:
In my opinion, this is the most direct possible shot through to New England without going near any metropolitan agglomerations. The plan was to detour north at Charlotte, NC. and follow I-81 all the way up to
Motorama Harrisburg, from whence my general solution has been to go east and up-around New York City through 287, then cutting north out of CT on I-91 and I-84. The upper half of this has been tried and verified many times.
I think this was a good decision. Not only was it smooth all the way, but the western VA and NC scenery subtracted from the boredom greatly. We passed through, and stopped in, a few small towns and villages nestled in the Appalachians, places that I’m sure high flying urban folks around here don’t give a shit about. It was, in my view, a more authentic American experience.
Stopping for a fuel and breakfast somewhere north of Roanoke, VA.
daily van bro
I saw something which looked out of place across the street at a convenience store. Turns out it’s a Greenbrier, one of the original American compact vans built to compete with the VW bus! These are rear-engined, just like the VW bus, but the Ford Econoline of the same era was mid-engined and rear wheel drive, and the layout was directly ported and evolved by the Japanese. So, really this is an evolutionary ancestor to Mikuvan.
It was also on sale. I called up the seller, but sadly the price asked was out of what I had in my pocket at the time. If I were into these things, though, it would be a very fair price for a vehicle in as good visual condition, and as good running condition as the seller described.
Compared to almost all modern cars, I’m pretty damned small, but the Greenbrier was somehow even smaller. And it had 3 rows of bench seats.
The rest of the trip up through Harrisburg and beyond was pretty standard. We arrived back in around 1:30 AM (that is, 0130EDT Wednesday 9/4). And so that concludes Dragon*Con 2013. A pretty delightful adventure filled with working robots and now-most-definitely-working vans.
Well, okay, I did have to rebuild my A/C blower motor again, in the Georgia Tech parking lot. Remember those brushes I installed? They were backwards, and they ate through the copper bus wire after a few thousand miles. A random 200W scooter motor turned out to have the exact same size brushes, and saved the day.
Maker Panel 2013
Here’s where I (finally) post the presentation from the 2013 Maker Resources panel, and some related links, in one place! The panel happened on Friday evening at 7PM, and I had a pretty full house for most of it. Unfortunately I once again neglected to bring my video camera to the event, but I did notice quite a few folks taking video. If you have some high quality video of the panel, I’d like to include it here.
The panel was broader in scope than just “where to buy stuff” which I did in 2012. It put more emphasis on CAD software and transferring designs to parts using digital fabrication techniques (waterjets, lasers, etc.), and in general how to design better things. I tried to include some CAD program demos of stuff like Sketchup, freeCAD, and Solidworks/Inventor, but I actually ran so far over time that the director had to step in and cut me off (Sorry Val!). Maybe next year.
Also included as part of side discussion were the slides from last year with general parts & resources.
Here’s the list of stuff I said I’d put up like two weeks ago: